Debian package was reported as fixed but it is not #6143
Replies: 2 comments 1 reply
-
Hello @beltran-rubo We are already working on this matter - aquasecurity/trivy-db#381. Regards, Dmitriy |
Beta Was this translation helpful? Give feedback.
-
Hi, I posted this in the subthread - but posting here in case you managed to solve this @beltran-rubo Any chance you can assist? Hi there. I am new to this - could you kindly assist with the issue I am having? On 7 February 2024, we ran our pipeline, with docker installing this version via apt-get - "libgnutls30=3.7.1-5+deb11u3". It worked fine. On 15 February 2024 we ran same pipeline with same settings, and it failed with exit code 100. I presume now, that this means that the version tag "3.7.1-5+deb11u3" does not exist anymore - is that correct? I consequently used this thread to determine what would be the correct version tag to use: https://avd.aquasec.com/nvd/2024/cve-2024-0567/ I tried "libgnutls30=3.7.1-5+deb11u4" - it does appear to install this version, however Trivy flags a vulnerability. I then tried "libgnutls30=3.7.1-5+deb11u5" - exit code 100 - it does not appear that this version currently exists? In this context I am somewhat new to this - could you kindly explain if/when this will be ready for us, and will effectively address the above vulnerability? Finally, I do see mention made of libgnutls28 instead of 30 in various threads and instances. Is it correct for me to use "libgnutls30=3.7.1-5+deb11u5" or "libgnutls28=3.7.1-5+deb11u5" - note the difference 28/30? Thank you |
Beta Was this translation helpful? Give feedback.
-
IDs
CVE-2024-0567
Description
The Debian 11 package "gnutls30" is reported as fixed when the upstream version it is not.
See https://security-tracker.debian.org/tracker/CVE-2024-0567 for bullseye the latest package available is 3.7.1-5+deb11u4
and the Trivy report shows the version 3.7.1-5+deb11u5 is available when it is not.
│ libgnutls30 │ CVE-2024-0567 │ HIGH │ fixed │ 3.7.1-5+deb11u3 │ 3.7.1-5+deb11u5
Would be possible Trivy is detecting the source package version that is available and not the binary package into the repository?
Reproduction Steps
Target
Container Image
Scanner
Vulnerability
Target OS
No response
Debug Output
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