We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug The CNA rules state that CVEs starting with CVE-1900 SHOULD be used for example purposes
CVE-1900
To Reproduce Mentioned in the following files:
SSVC/data/schema_examples/CVE-1969-0000-Decision_Point_Value_Selection.json
Line 4 in 311a170
SSVC/data/schema/v1/Decision_Point_Value_Selection-1-0-1.schema.json
Line 8 in 311a170
Expected behavior Example CVEs should start with CVE-1900
Screenshots none
Platform details none
Additional context @sei-vsarvepalli as discussed today
The text was updated successfully, but these errors were encountered:
related also - CVEProject/cve-schema#310
Sorry, something went wrong.
Also fixed for Issue CERTCC#665
337edce
Spelling error fix in Decision Point Value Selection cvvs to cvss (#664)
8f0123d
* Spelling error fix in Decision Point Value Selection cvvs to cvss * Moved CVE-1969 to recommend CVE-1900 example see https://github.com/CVEProject/cve-schema/releases * Also fixed for Issue #665
This is resolved in both the publish (public website) and the main branches which replaces the CVE file with CVE-1900-1234-Decision_Point_Value_Selection.json
publish
main
Vijay
No branches or pull requests
Describe the bug
The CNA rules state that CVEs starting with
CVE-1900
SHOULD be used for example purposesTo Reproduce
Mentioned in the following files:
SSVC/data/schema_examples/CVE-1969-0000-Decision_Point_Value_Selection.json
Line 4 in 311a170
SSVC/data/schema/v1/Decision_Point_Value_Selection-1-0-1.schema.json
Line 8 in 311a170
Expected behavior
Example CVEs should start with CVE-1900
Screenshots
none
Platform details
none
Additional context
@sei-vsarvepalli as discussed today
The text was updated successfully, but these errors were encountered: