Digging Into Your App's Container Image Layers for Sneaky Vulnerabilities
summary
Uses Trivy to scan a Spring Boot image (initial run shows ~200 vulnerabilities) and narrows to actionable items with --severity=CRITICAL and --ignore-unfixed, then uses wagoodman’s dive layer explorer to pinpoint the exact Docker layer that copies a vulnerable xstream jar brought in by a Helm plugin from the builder stage. Demonstrates using mvn dependency:tree and effective-pom to confirm it’s not in the source, shows multi-stage Dockerfile pitfalls, leaking build-time secrets via ARG misuse, and fixing issues by updating base images or plugin versions.
AI-written summary · about
chapters (5)
related talks
46mStranger Danger: Securing Your Java Containers by Breaking In
38mSo. Many. Vulnerabilities. Why are containers such a mess...
24mSecuring Container Workloads
09mSpotlight on a New Feature of the JFrog Platform
30mMaster the Container Security Model with
52mSecuring Your Java Containers by Breaking In
35mSecuring Containers by Breaking In
47mSecuring Containers By Breaking In
