-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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
gh-112844: Fix xz CPE identifier #117656
gh-112844: Fix xz CPE identifier #117656
Conversation
LGTM. How do we interpret that reference? Since |
@zooba You have to go the the CVE Dictionary and search it or download the entire dataset. They helpfully disallow queries under 3 characters so "xz" won't do, and this caused me to not find the right CPE. Searching for "xz tukaani" lets you find the right one and confirm the linkage to CVE-2024-3094 (xz-utils backdoor). |
I just searched the whole string as shown in the file and it found the right one (not the one with the most recent CVE, of course). So that's good to know. |
Thanks @sethmlarson for the PR, and @zooba for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
(cherry picked from commit d70ee13) Co-authored-by: Seth Michael Larson <seth@python.org>
GH-117951 is a backport of this pull request to the 3.12 branch. |
Thanks @zooba! 🙏 |
Previous CPE identifier was for an xz Go package, not for the upstream package (isn't CPE fun?) Confirmed that this CPE works to detect the recent backdoor CVE by manually faking the metadata for 5.6.1 and running Grype. Will need a backport to 3.12 as well.