-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add guidance about year portion of the ID #7
Comments
Somewhat related, |
This would be helpful. My impression was that the year specified when the issue was first disclosed, not when it was first publicly disclosed. |
Signed-off-by: Art Manion <zmanion@protonmail.com>
I'm mildly in favor of using the year of public disclosure, otherwise only the CNA (and possibly a few others involved in a private disclosure) would know or care about the year of pre-public disclosure. CVE is about publicly disclosed vulnerabilities, so the date (year) should be based on that. Also the proposed change is a recommendation not a requirement:
|
Since adding or removing SHOULD and MAY directives aren't breaking changes to the rules, I'm super on board with this clarification. |
Add guidance to the assignment rules about the year portion of the ID.
Confirm that the year part of a CVE ID SHOULD (or MUST?) be the calendar year in which the vulnerability was first publicly disclosed or develop correct guidance.
The text was updated successfully, but these errors were encountered: