-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Regression in 0.50.0 - SIGSEGV scanning some container images #6344
Comments
Yeah came here to report the same. 👍🏽 For me it's the |
This happens because spdx file from image doesn't contains required CreationInfo field.
We already have #6346 to avoid panic for these SPDX files. |
We have to downgrade our trivy-server because of <aquasecurity/trivy#6344>, so I'm downgrading here, too, to keep the versions matching.
Same happening to me for |
Also on macos-arm64 with redis:7.2.4-alpine@sha256:641c365890fc79f182fb198c80ee807d040b9cfdb19cceb7f10c55a268d212b8. The 0.49.1 does it fine. Regards |
Same with rabbitmq:3:13-alpine |
Discussed in #6343
Originally posted by weili-jiang March 19, 2024
Description
Scanning some Docker images using 0.50.0 crashes with a SIGSEGV but were able to complete using Trivy 0.49.1.
Example of problematic image:
rabbitmq
official Docker image: https://hub.docker.com/_/rabbitmqDesired Behavior
Scan completes
Actual Behavior
Crashed with SIGSEGV
Reproduction Steps
1. Run `trivy image rabbitmq`
Target
Container Image
Scanner
Vulnerability
Output Format
Table
Mode
Standalone
Debug Output
Operating System
Linux/Docker
Version
Checklist
trivy image --reset
The text was updated successfully, but these errors were encountered: