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

Why not every CVE collected in GHSA? #2451

Open
JustinB1eber opened this issue Jun 25, 2023 · 3 comments
Open

Why not every CVE collected in GHSA? #2451

JustinB1eber opened this issue Jun 25, 2023 · 3 comments

Comments

@JustinB1eber
Copy link

Accroding to the document, it seems that github security advisory database would collect every CVE from NVD
image
But I have seen a few CVEs not in GHSA, neither reviewed nor unreviewed, e.g. CVE-2023-31058

@spcompanyf15t33n
Copy link

unreviewed

@spcompanyf15t33n
Copy link

Accroding to the document, it seems that github security advisory database would collect every CVE from NVD
image
But I have seen a few CVEs not in GHSA, neither reviewed nor unreviewed, e.g. CVE-2023-31058

@KateCatlin
Copy link
Collaborator

Hey @JustinB1eber, thank you so much for writing in about this. We do have one small gap in our data, which is advisories originated from a GitHub security advisory which get a CVE but which are not part of our supported ecosystems. This is a date flow error that we are planning to correct.

Can you share any CVEs that you find which are not in our Advisory Database so I can confirm the issue is the same and that we don't have any other leaks?

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

3 participants