Wargames - Java vulnerabilities and why you should care
summary
Explains concrete Java security plumbing: how NVD/CVE/CVSS work and why CVE-2021-44228 (Log4Shell) scores 10.0 CVSS3.1, why a JDK left at 17 GA accumulates ~55 unpatched CVEs, and why supply‑chain attacks rise ~742%. Shows actionable fixes: use SDKMAN and jdeps, run Snyk or SonarQube in CI, and build tailored runtimes with jlink (example: JDK from 339 MB to 48 MB by using 11 modules). Demonstrates a runtime scanner integrated into the JVM with <1% overhead that flags unused vulnerable classes.
AI-written summary · about
chapters (8)
- 0:00Welcome and introduction
- 1:05Java vulnerabilities overview
- 9:29Java security in 21st century
- 19:24CPU vs PSU updates explained
- 22:36Modular runtime with JLink
- 25:50Software supply chain risks
- 32:52Shift left and validate security
- 45:19Key takeaways and best practices
related talks
44mWargames - Java Vulnerabilities and Why You Should Care
45mWargames - Java vulnerabilities and why you should care
56mThe Anatomy of Java Vulnerabilities
49mThe Anatomy of Java Vulnerabilities
02h 38mJava application security the hard way - a workshop for the serious developer
46mThe Anatomy of Java Vulnerabilities
48mThe Hidden Security Hazards in Your Java Stack
48mCommon vulnerabilities you wish your Java app didn't have!