-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
[SECURITY] publish a VEX/VDR #1183
Comments
Re-reading @stevespringett article on the OWASP website (https://owasp.org/blog/2023/02/07/vdr-vex-comparison), and searching for the authoritative reference regarding VDR, I noticed that the NIST SP 800-161, originally from 2015, have been superseded: The new revision can be found here, published in May 2022, so after @stevespringett article, but including updates as of 11-01-2024 (sic): Whatever the reason, as of today, at least this mention of this NIST SP is out of date in the CDX project: Note that I do not consider that this makes the VDR concept obsolete. Just that the NIST can't be referred to, except for historical purposes. |
thanks for the update 👍 |
(Indeed, will do, just noticed this lib is not the right place for this. It's the only oppened issue about VDR I could found on CycloneDX as a whole.) EDIT: done |
This library might have/had vulnerabilities, see https://github.com/CycloneDX/cyclonedx-javascript-library/security/advisories
and #1061
We intend to have all security issues closed/fixed eventually, if not already.
We should make this transparent to the user, by publishing a Vulnerability Exploitability eXchange (VEX) documentand and a Vulnerability Disclosure Report (VDR).
Expected outcome:
{vex,vdr}.cdx.*
, instead of onesecurity.cdx.*
for the content, see distinction https://github.com/CycloneDX/bom-examples/blob/master/VDR/README.md#distinction-between-vulnerability-disclosure-report-vdr-and-vulnerability-exploitability-exchange-vex
The text was updated successfully, but these errors were encountered: