Replies: 1 comment 8 replies
-
|
Hello @delsner Trivy uses digest for But it works with digest: ➜ cat test.openvex.json
{
"@context": "https://openvex.dev/ns/v0.2.0",
"@id": "https://openvex.dev/docs/public/vex-7044ebb8ba3b8bdd56d7c48a0f7d4924acf978bd643f3df2e22fdea26b9c315f",
"author": "Unknown Author",
"timestamp": "2025-04-28T07:48:07.927732+02:00",
"version": 1,
"statements": [
{
"vulnerability": {
"name": "CVE-2025-22868"
},
"timestamp": "2025-04-28T07:48:07.927733+02:00",
"products": [
{
"@id": "pkg:oci/gitlab-runner@sha256%3A8fa48314b5662857f75e4338f9590fbd32d3eac4f52e0c43c313a2f104bd54f9",
"subcomponents": [
{
"@id": "pkg:golang/golang.org/x/[email protected]"
}
]
}
],
"status": "not_affected",
"justification": "vulnerable_code_not_present"
}
]
}
➜ trivy -q image gitlab/gitlab-runner:ubuntu-bleeding --vex test.openvex.json --show-suppressed
...
Suppressed Vulnerabilities (Total: 1)
┌─────────────────────┬────────────────┬──────────┬──────────────┬─────────────────────────────┬───────────────────┐
│ Library │ Vulnerability │ Severity │ Status │ Statement │ Source │
├─────────────────────┼────────────────┼──────────┼──────────────┼─────────────────────────────┼───────────────────┤
│ golang.org/x/oauth2 │ CVE-2025-22868 │ HIGH │ not_affected │ vulnerable_code_not_present │ test.openvex.json │
└─────────────────────┴────────────────┴──────────┴──────────────┴─────────────────────────────┴───────────────────┘
...
Regards, Dmitriy |
Beta Was this translation helpful? Give feedback.
8 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.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
I'm trying to exclude findings from the
gitlab/gitlab-runnerimage using a VEX document.Here's the command I use:
Where the content of the VEX file is:
{ "@context": "https://openvex.dev/ns/v0.2.0", "@id": "https://openvex.dev/docs/public/vex-7044ebb8ba3b8bdd56d7c48a0f7d4924acf978bd643f3df2e22fdea26b9c315f", "author": "Unknown Author", "timestamp": "2025-04-28T07:48:07.927732+02:00", "version": 1, "statements": [ { "vulnerability": { "name": "CVE-2025-22868" }, "timestamp": "2025-04-28T07:48:07.927733+02:00", "products": [ { "@id": "pkg:oci/gitlab/gitlab-runner:ubuntu-bleeding", "subcomponents": [ { "@id": "pkg:golang/golang.org/x/[email protected]" } ] } ], "status": "not_affected", "justification": "vulnerable_code_not_present" } ] }I also tried with specifying the version as sha256 digest instead of the tag
:ubuntu-bleeding.What am I doing wrong or is this a bug?
Desired Behavior
I expected the finding corresponding to the excluded CVE to be suppressed.
The JSON output file should contain a section
ExperimentalModifiedFindingswhich lists the suppressed finding.It has done so for other images before.
Actual Behavior
No
ExperimentalModifiedFindingssection in JSON and the finding is not excluded from the reported CVEs.Reproduction Steps
Target
Container Image
Scanner
Vulnerability
Output Format
JSON
Mode
Standalone
Debug Output
Operating System
macOS and Linux
Version
Checklist
trivy clean --allBeta Was this translation helpful? Give feedback.
All reactions