-
Notifications
You must be signed in to change notification settings - Fork 121
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 "severity" to vuln/core JSON vulnerability feed #1372
Comments
SGTM. Would you like to update the current database and I'll make sure to update our security release process to include severity for the next ones? |
Sounds good, I'll create a PR shortly. Note that also |
|
Ah ok great.
B - Less nice, but doesn't break the schema -
What would you prefer? |
cve is a list because sometimes we include a previous CVE to this new vulnerability. Most of the time, they will have the same severity. So, using |
Gotcha, ok great I will add a single value with the highest severity |
Fixed in #1374 |
It would be great to include the vulnerability's severity in the JSON files generated under
vuln/core
.For example for 146.json -
{ "cve": [ "CVE-2024-37372" ], + "severity": "low", "vulnerable": "20.x || 22.x", "patched": "^20.15.1 || ^22.4.1", "ref": "https://nodejs.org/en/blog/vulnerability/july-2024-security-releases/", "overview": "The Permission Model assumes that any path starting with two backslashes \\\\ has a four-character prefix that can be ignored, which is not always true. This subtle bug leads to vulnerable edge cases.\n\nThis vulnerability affects Windows users of the Node.js Permission Model in version v20.x and v22.x", "affectedEnvironments": ["all"] }
The text was updated successfully, but these errors were encountered: