We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When the Debian metadata lists a fix version, the status is assumed to be "fixed", even if the package has not yet been released.
This is noticeable in CVE-2023-5981: https://security-tracker.debian.org/tracker/CVE-2023-5981 shows that the fix has not been released in "bullseye", but the Trivy DB shows fixed for this.
The text was updated successfully, but these errors were encountered:
if trivy relies on this feed https://security-tracker.debian.org/tracker/data/json... it won't havve these "fixed" issues... this json feed has more accurate indications about the fixed versions. I think trivy-db should use it instead of https://salsa.debian.org/security-tracker-team/security-tracker
Sorry, something went wrong.
No branches or pull requests
When the Debian metadata lists a fix version, the status is assumed to be "fixed", even if the package has not yet been released.
This is noticeable in CVE-2023-5981: https://security-tracker.debian.org/tracker/CVE-2023-5981 shows that the fix has not been released in "bullseye", but the Trivy DB shows fixed for this.
The text was updated successfully, but these errors were encountered: