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

Create the example.com of CVE IDs #19

Open
todb opened this issue Jun 21, 2023 · 2 comments
Open

Create the example.com of CVE IDs #19

todb opened this issue Jun 21, 2023 · 2 comments

Comments

@todb
Copy link

todb commented Jun 21, 2023

This came up in some conversation, and I think it would be a fine idea to reserve one CVE ID as a reference CVE.

I gave it a shot, here: https://github.com/todb/junkdrawer/blob/main/CVE-1969-12345.json

And I'm happy to publish and maintain it in the real directory if I get some kind of blessing.

@todb
Copy link
Author

todb commented Jun 21, 2023

Features:

  • Numbered and named in an obviously example-looking way.
  • Text is multiline
  • Text includes escaped Javascript
  • Text includes the EICAR test file string
  • References are resolvable
  • References include a raw EICAR test file
  • Affected ranges exercise both semver and git commit ranges
  • CVSS score is a MEDIUM, 6.7, which is rare but possible in the distribution
  • Has a CWE and CAPEC problem type.
  • Has an example custom tag

There are more fields to fill in, but some number of fields should be left blank in order for downstream parsers to test blankness. Not sure which are the most commonly parsed but also optional fields. Platforms would be my guess.

If people don't hate this CVE ID, I'll publish it.

@zmanion
Copy link
Contributor

zmanion commented Jun 12, 2024

The ID should start with 'CVE-1900-'.

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

2 participants