Serial Killer Silently Pwning Your Java Endpoints
OWASPBNL_Java_Deserialization OWASPBNL_Java_Deserialization
Finding Vulnerabili;es & Gadgets in the Code SAST Tips
Who Should Check for What? 1. Check your endpoints for those accep;ng (untrusted) serialized data 2. Check your code for poten;al gadgets, which could be used in deserializa@on aEacks where your library / framework is used Also the ClassPath of the app-server can host exploitable gadgets Problem: "Gadget Space" is too big Typical app-server based deployments have hundreds of JARs in ClassPath SAST tools might help for both checks… Such as HPE Security For@fy or the OpenSource FindSecBugs 31
- Page 1 and 2: Chris;an Schneider Serial Killer: S
- Page 3 and 4: Standing on the Shoulder of Giants
- Page 5 and 6: AWack Surface Usages of Java serial
- Page 7 and 8: Triggering Execu;on via "Magic Meth
- Page 9 and 10: Exploi;ng "Magic Methods" But what
- Page 11 and 12: Exploi;ng Invoca;onHandler (IH) Gad
- Page 13 and 14: New RCE Gadget in BeanShell (CVE-20
- Page 15 and 16: New RCE Gadget in Jython (CVE pendi
- Page 17 and 18: Exis;ng Mi;ga;on Advice Simply remo
- Page 19 and 20: Exis;ng Mi;ga;on Advice Simply remo
- Page 21 and 22: How did vendors handle this recentl
- Page 23 and 24: Is this for real or is this just fa
- Page 25 and 26: Now with home delivery javax.media.
- Page 27 and 28: Is it just Java Serializa;on? XStre
- Page 29: XStream, can you run readObject()?
- Page 33 and 34: High-Level Gadget Categories Gadget
- Page 35 and 36: What to Check During Pentests? DAST
- Page 37 and 38: Ac;ve Vulnerability Scanning Some B
- Page 39 and 40: How to Harden Your Applica;ons? DO
- Page 41: Chris;an Schneider @cschneider4711
Finding Vulnerabili;es & Gadgets in the Code<br />
SAST Tips
Change language