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

CNA Rules: Clarify "identify" in 5.1 #7

Open
andrewpollock opened this issue Sep 19, 2024 · 1 comment
Open

CNA Rules: Clarify "identify" in 5.1 #7

andrewpollock opened this issue Sep 19, 2024 · 1 comment

Comments

@andrewpollock
Copy link

"Picture in my head/picture in your head" type of stuff...

My interest is in aggregate machine-readability of CVEs (at scale).

I have encountered numerous responses in recent times expressing the belief that if the items discussed in section 5.1 of the CNA rules are provided in the human-readable description field, that this satisfies the CNA rules. It would be good if the CNA rules were unambiguous about this.

5.1.1 SHOULD contain sufficient information to uniquely identify the Vulnerability and distinguish it from similar Vulnerabilities.
5.1.3 MUST identify at least one affected Product using information such as Supplier and Product names, versions, and dates.
5.1.4 MUST identify at least one Product as “affected” or “unknown” (with the possibility of being affected).
5.1.5 SHOULD identify Fixed versions of Products.
5.1.7 MUST identify the type of Vulnerability. The CVE record SHOULD use the Common Weakness Enumeration (CWE) to classify the type or cause of the Vulnerability. A CVE Record MAY contain multiple types or causes of the Vulnerability.

@andrewpollock
Copy link
Author

/cc @zmanion @jayjacobs @jgamblin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant