GoLang Prometheus module versions trigger false CVE-2019-3826 alert #4479
Replies: 6 comments 3 replies
-
Same one? @DmitriyLewen |
Beta Was this translation helpful? Give feedback.
-
Yes, same one. We can close it. |
Beta Was this translation helpful? Give feedback.
-
Duplicate of #2992 |
Beta Was this translation helpful? Give feedback.
-
@DmitriyLewen Did you guys change something? Because with no changes on my end or in the |
Beta Was this translation helpful? Give feedback.
-
The security vulnerability was not even in the go code. |
Beta Was this translation helpful? Give feedback.
-
IDs
CVE-2019-3826
Description
Scanning a GoLang based image that uses https://github.com/prometheus/prometheus gives the following scan results:
That's because the module is https://pkg.go.dev/github.com/prometheus/[email protected] that corresponds to the latest Prometheus version (2.44.0).
Prometheus README about the weird Go module numbering:
https://github.com/prometheus/prometheus#prometheus-code-base
Quoting from the README:
Prometheus code base
In order to comply with go mod rules, Prometheus release number do not exactly match Go module releases. For the Prometheus v2.y.z releases, we are publishing equivalent v0.y.z tags.
Therefore, a user that would want to use Prometheus v2.35.0 as a library could do:
Reproduction Steps
1. Run the scanner: docker run --rm -it -v $HOME/trivy-cache:/root/.cache/ aquasec/trivy:0.41.0 image devopsfaith/krakend:2.3.2
Version
Checklist
-f json
that shows data sources and confirmed that the security advisory in data sources was correctBeta Was this translation helpful? Give feedback.
All reactions