V1.20 reports not consistent with scout.docker.com
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Reproduce the reports with the shown docker scout cves and docker scout vex get commands for darkedges/pingaccess:8.3.4-hi. Compare the web result, CLI output, and the locally loaded pa-vex.json, then inspect the linked VEX statements. Done means identifying why the views differ and documenting or correcting the inconsistent behavior.
Written by the indexing model from the issue text.
Description
it reports
but when ran via the comand line
docker scout cves darkedges/pingaccess:8.3.4-hi
i New version 1.21.0 available (installed version is 1.20.0) at https://github.com/docker/scout-cli
v SBOM obtained from attestation, 278 packages found
v Provenance obtained from attestation
v VEX statements obtained from attestation
x Detected 29 vulnerable packages with a total of 52 vulnerabilities
When I get an use the vex locally
docker scout vex get darkedges/pingaccess:8.3.4-hi --output pa-vex.json
i New version 1.21.0 available (installed version is 1.20.0) at https://github.com/docker/scout-cli
v SBOM obtained from attestation, 278 packages found
v Provenance obtained from attestation
v Found 53 VEX attestations for image
v Report written to pa-vex.json
docker scout cves darkedges/pingaccess:8.3.4-hi --vex-location pa-vex.json
i New version 1.21.0 available (installed version is 1.20.0) at https://github.com/docker/scout-cli
v SBOM obtained from attestation, 278 packages found
v Provenance obtained from attestation
v Loaded 1 VEX document
v VEX statements obtained from attestation
x Detected 8 vulnerable packages with a total of 6 vulnerabilities
it appears that I am not able to get a consistent view.
- CLI without a local vex shows all vulnerability despites having a
statusofnot affected [vulnerable code not in execute path] - CLI with local vex extract from container shows more vulnerabilities than the web interface.
Vex Statements are at https://github.com/darkedges/trivy-vex-demo/blob/main/vex/statements-scout-darkedges/
- Dominant language
- Shell
- Stars
- 454
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/scout-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
allstar
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
panic: nil deref in createVCS() scanning multi-arch image by tag when no attestation sidecar exists Open
Difficulty 4/5 3-5 days Newbie friendliness 64/100
All issues in docker/scout-cli
Similar issues
-
good-start
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
VilnaCRM-Org/user-service#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
area:jail bug security severity:low track:open-source
Difficulty 1/5 Under an hour Newbie friendliness 75/100