jfrog / jfrog/jfrog-cli-security
jf docker scan fails to extract indexer
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Describe the bug
When I run jf docker scan command - I receive a result different from the Xray UI in the artifactory. Xray shows vulnerabilities with fixed versions, but jf docker scan doesn't yet show the fixed versions for the same vulnerabilities.
Current behavior
In the logs I see the following error:
2024-02-06T15:15:20.570Z [jfxia] [WARN ] [] [archive_mgr:297 ] [TODOContext ] Failed to extract file builtins.7.gz (root path: /tmp/jfrog.cli.temp.-1707232512-3746508436/33cb6ae2-4eaf-43d5-6d35-347c62e69bb8/170723251483866449/). Would be treated as generic. err : failed to decompress file: /tmp/jfrog.cli.temp.-1707232512-3746508436/33cb6ae2-4eaf-43d5-6d35-347c62e69bb8/170723252057034829/builtins.7.gz
--- at /go/src/jfrog.com/xray/backend/indexer/indexer_core/decompressor.go:23 (Decompressor.DeepArchiveScan) ---
Caused by: Archive extractor error, gzip: invalid header
Reproduction steps
No response
Expected behavior
I want to see the same result as in Xray UI
JFrog CLI version
2.52.10
Operating system type and version
ubuntu 22
JFrog Artifactory version
7.71.8
JFrog Xray version
3.85.5
Contributor guide
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.
Research direction
Start by investigating the jf docker scan path and the logged indexer extraction failure for builtins.7.gz, using the reported CLI, Artifactory, Xray, and Ubuntu versions. Reproduction steps and named source files are not provided; done means the scan extracts the image correctly and reports fixed versions consistent with the Xray UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100