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

specify rust as target software component in CPE #2400

Conversation

westonsteimel
Copy link
Contributor

This is specifically a vulnerability that applies to the arrayfire rust bindings which should be distinguished from bindings for other ecosystems to help prevent mismatches like with pypa/advisory-database#99

Signed-off-by: Weston Steimel weston.steimel@anchore.com

@westonsteimel
Copy link
Contributor Author

westonsteimel commented Sep 9, 2022

@kurtseifried and @joshbressers, I don't remember if this is exactly how we specify overrides of the nvd namespace in GSD - I do have alot more cases where I'd like to modify CPEs, version ranges, etc, but wanted to ensure I have the format figured out before I go too far down that road. Ideally at some point in the future we'd have a good way to automatically feed these suggested updates back to NVD, but I know that is going to be challenging

This is specifically a vulnerability that applies to the arrayfire rust bindings which should be distinguished from bindings for other ecosystems to help prevent
mismatches like with pypa/advisory-database#99

Signed-off-by: Weston Steimel <weston.steimel@anchore.com>
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

Successfully merging this pull request may close these issues.

None yet

1 participant