Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

original assigner vs. owner #294

Open
zmanion opened this issue Mar 18, 2024 · 5 comments
Open

original assigner vs. owner #294

zmanion opened this issue Mar 18, 2024 · 5 comments
Labels
bug Something isn't working Needs Discussion Discuss in a future QWG meeting or on mailing list section:metadata Schema location is metadata

Comments

@zmanion
Copy link
Contributor

zmanion commented Mar 18, 2024

Copied from CVEProject/automation-working-group#116

On the 2023-01-11 SPWG meeting, during a discussion about bulk download, this came up:

The assigning CNA is recorded in the JSON schema (assignerOrgId), this is effectively the owning CNA at the time of assignment
The owner of a record can change
Ownership and the transaction log are stored somewhere, not explicitly in JSON 5
3.a. Ownership might have been stored in JSON 4 (but I don't readily see where)
JSON 5.0 does not provide explicit "owner" fields
CVE Services, with knowledge of the non-public ownership, can (broken at the moment?) provide a CNA with their currently owned records.

JSON 5 alone, e.g., as a bulk download format, contains neither ownership information nor transaction information.

Regardless of where ownership and transaction information is stored, it should be available publicly.

Related to/partial duplicate of: CVEProject/cve-website#1224

owning_cna can be accessed via Services API:

https://cveawg.mitre.org/api/cve-id/CVE-2020-28367
https://cveawg.mitre.org/api/cve/CVE-2020-28367

@zmanion
Copy link
Contributor Author

zmanion commented Mar 18, 2024

Proposal: Add new ownerCnaId and ownerCnaShortName fields to JSON schema, basically matching assignerOrgId and assignerShortName.

Unless the owner* values are filled out, treat them as equal to assginer*.

Both owner* values must be filled out, which I think is similar to assigner*, and *ShortName should be looked up based on *OrgId.

I think this means that owner MUST be a CNA, is that a problem?

@zmanion
Copy link
Contributor Author

zmanion commented Mar 18, 2024

Proposal 2: Make ownership (and other?) change/transaction logs/history public. Possibly within a CVE record, so there is one self-contained place to look. This should probably be a separate issue.

@zmanion
Copy link
Contributor Author

zmanion commented Mar 18, 2024

Overall, eliminate or minimze the need for separate sources of CVE entry data.

https://cveawg.mitre.org/api/cve-id/CVE-2020-28367

"cve_id":"CVE-2020-28367",
"cve_year":"2020",
"state":"PUBLISHED",
"owning_cna":"Go",
"dateUpdated":"2022-12-28T14:23:56.914Z"

Aside from owning_cna, the rest of this information is available within a CVE record, with the possible exception of cve_year.

If "cve_year" is not just the year part of the CVE ID then we need to discuss.

@jayjacobs jayjacobs added the bug Something isn't working label Oct 18, 2024
@jayjacobs jayjacobs added Needs Discussion Discuss in a future QWG meeting or on mailing list section:metadata Schema location is metadata labels Oct 31, 2024
@jayjacobs
Copy link
Collaborator

Related to AWG CVEProject/automation-working-group#133

@jayjacobs
Copy link
Collaborator

Currently the cveMetadata has the assignerOrgId and assignerShortName, which are "the organization to which the CVE ID was originally assigned" and the cna.providerMetadata has orgId and shortName which are "The container provider". Presumably the providerMeta and the "owning CNA" would be the exact same thing? Or are these different?

I do think the second proposal "Make ownership (and other?) change/transaction logs/history public." should be separate issue and discussed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Needs Discussion Discuss in a future QWG meeting or on mailing list section:metadata Schema location is metadata
Projects
None yet
Development

No branches or pull requests

2 participants