-
Notifications
You must be signed in to change notification settings - Fork 621
False Positive: Multiple old CVEs in chromium 134.0.6998.117 for apk ecosystem. #2581
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
Comments
Thanks for the issue @simonc6372 - I was able to reproduce with your steps - so thanks also for that. This could be 'bad data' from nvd.
The NVD URL indicates:
|
We merged some data improvements for these ancient CVEs (see anchore/cve-data-enrichment#17 ). Tomorrow's grype database should no longer show these false positives. Thanks for the report! It would be nice to also contribute some NAKs to the Alpine package: https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/community/chromium/APKBUILD#L183 I'll do that if I get a chance, but anyone is welcome to beat me to it. |
What happened:
Grype 0.91.0, is detecting CVE-2013-6647 and multiple other old CVEs in a recent version of google chromium when this was fixed a long time ago.
I think the following are being detected due to no CPE
Looking at the JSON output of a scan, it looks like it's due to no version information in the CPE,
Looking at the detection for CVE-2013-6647 for example,
What you expected to happen:
no detection of CVE-2013-6647 and similar old CVEs.
How to reproduce it (as minimally and precisely as possible):
The
grafana/grafna-image-renderer:3.12.4
image is triggering this bug.Scanned with a default configuration.
Anything else we need to know?:
Environment:
grype version
:grype db list
:cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: