w3m in Alpine Linux 3.22 #8973
mbentley
started this conversation in
False Detection
Replies: 1 comment 3 replies
-
I tested how Alpine's apk compares these versions using Alpine Linux 3.20: $ docker run --rm alpine:3.20 apk version -t 0.5.3_git20250505-r0 0.5.3.20180125-r0
<
$ docker run --rm alpine:3.20 apk version -t 0.5.3.20180125-r0 0.5.3_git20250505-r0
> According to Alpine's version comparison logic (found in apk-tools source code), This is because:
So go-apk-version correctly considers the git version as older/lower than the stable version, which explains why these CVEs are flagged by Trivy. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
IDs
CVE-2018-6196, CVE-2018-6197, CVE-2022-38223, CVE-2018-6198, CVE-2023-38252, CVE-2023-38253
Description
When scanning an Alpine Linux 3.22.0 image that has the
w3m
package installed, the version is not detected properly due to what I am fairly certain isgit
being added to the version string. In 3.22,0.5.3_git20250505-r0
is the version number and in 3.21, it was0.5.3.20230718-r2
Reproduction Steps
Target
Container Image
Scanner
Vulnerability
Target OS
Alpine Linux 3.22
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