Your Docker Images Have 847 Vulnerabilities (And You'll Ignore Them All)

I ran Trivy on a production Node.js application last week. The output was 847 vulnerabilities. Not a typo. Eight hundred and forty-seven. I stared at my terminal for a solid minute. Where do you ev...

By · · 1 min read
Your Docker Images Have 847 Vulnerabilities (And You'll Ignore Them All)

Source: DEV Community

I ran Trivy on a production Node.js application last week. The output was 847 vulnerabilities. Not a typo. Eight hundred and forty-seven. I stared at my terminal for a solid minute. Where do you even start with that? Which ones matter? Which ones are in libraries I'm not even using? Which ones have known exploits versus theoretical risks? So I did what every developer does. I ignored all of them and shipped the image anyway. The CVE Fatigue Is Real Security scanners are doing their job. They're finding vulnerabilities. The problem is they find ALL the vulnerabilities and dump them in your lap with zero context. Here's what a typical scan looks like: $ trivy image myapp:latest Total: 847 (UNKNOWN: 23, LOW: 421, MEDIUM: 267, HIGH: 118, CRITICAL: 18) Okay, 18 critical vulnerabilities. That sounds important. Let me check them: CVE-2023-12345 in libssl1.1 (7.5 severity) CVE-2023-23456 in apt (9.8 severity) CVE-2022-34567 in systemd (8.1 severity) ...15 more critical issues Cool. Now what? D