Scan Container Images for Known CVEs
Scan the built image against a vulnerability database so a critical CVE in a base layer blocks the deploy.
Task
Implement trivy image --severity CRITICAL --exit-code 1 myapp:latest to close a known attack surface before the next security review finds it.
When to use this
A penetration test report flags the missing trivy image --severity CRITICAL --exit-code 1 myapp:latest as a medium-severity finding on a public endpoint.
Prerequisites
- A running application with the vulnerable endpoint
- Access to security headers or middleware config
Steps
1. Configure trivy image --severity CRITICAL --exit-code 1 myapp:latest in the project configuration file with the recommended defaults.
trivy image --severity CRITICAL --exit-code 1 myapp:latest
Expected output: The configuration is accepted and trivy image --severity CRITICAL --exit-code 1 myapp:latest runs without errors on the first invocation.
2. Run the check locally to verify trivy image --severity CRITICAL --exit-code 1 myapp:latest produces the expected result before pushing.
pnpm test
Expected output: Local run matches CI behavior; no surprises after push.
3. Add the gate to the CI pipeline so trivy image --severity CRITICAL --exit-code 1 myapp:latest blocks merge on failure.
- name: Run add container image scan
run: pnpm test
Expected output: Pull requests with failing trivy image --severity CRITICAL --exit-code 1 myapp:latest are blocked from merging.
Troubleshooting
Problem
The check passes locally but fails in CI
Solution
Pin dependency versions and the runtime to match CI exactly; reproduce with the same Docker image or act.
Problem
Configuration is rejected with a schema error
Solution
Check the tool version matches the config schema; older versions may not support newer fields.
Limitations
- The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
- Configuration drift is possible if someone edits settings outside version control.
Close the attack surface
Start by measuring the problem. Scan the built image against a vulnerability database so a critical CVE in a base layer blocks the deploy. The most common mistake is adding the gate without first confirming it catches the issue you care about. Run trivy image –severity CRITICAL –exit-code 1 myapp:latest against the current codebase and inspect the output before wiring it into CI.
trivy image --severity CRITICAL --exit-code 1 myapp:latestVerify and monitor
Once the gate is in place, make failures actionable. A failing trivy image –severity CRITICAL –exit-code 1 myapp:latest should point to the exact file and line, not a generic error. Pin the tool version in the lockfile so a upstream release does not silently change behavior. Review the gate output in every pull request just like a test result.