Skip to content
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

Wrong version of git causes false positive in Jenkins docker image scan #3663

Open
Bruceliu-rs opened this issue Feb 14, 2025 · 0 comments
Open
Labels
bug Something isn't working

Comments

@Bruceliu-rs
Copy link

What happened:
I run this cmd to scan my docker Jenkins image based on Debian.
syft docker.io/jenkins/jenkins:2.488 -o cyclonedx-json=sbom.syft.json
there are 13 vulnerabilities reported for git.
here is the git version generated:
**1:**2.39.5-0+deb12u1

What you expected to happen:
The version is wrong, it should be "2.39.5-0+deb12u1", without "1:"

Image

for example, CVE-2024-32465 and CVE-2023-25652 are reported, but they should be fixed in this version:
https://security-tracker.debian.org/tracker/CVE-2024-32465
https://security-tracker.debian.org/tracker/CVE-2023-25652

Steps to reproduce the issue:
syft docker.io/jenkins/jenkins:2.488 -o cyclonedx-json=sbom.syft.json
and upload the json into dependency track website.

Anything else we need to know?:
aquasecurity trivy didn't report the false positive for the same docker image.
If I manually create a git component in dependency track and with the correct version number, it won't report any vulns.

Environment:

Thanks.

@Bruceliu-rs Bruceliu-rs added the bug Something isn't working label Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

1 participant