What problem does it solve?
Java white-box auditors need a systematic way to determine whether deserialization, XXE, and SSTI vulnerabilities actually exist in source code, including entry-point identification, data-flow tracing, gadget chain availability, and parser security configuration checks.
Core Features & Use Cases
- Java Deserialization Audit: Identify ObjectInputStream/XMLDecoder entry points, trace data sources (HTTP, RMI, JMS, cache, cookies), and evaluate classpath gadget chain availability against commons-collections, commons-beanutils, spring-core, Groovy, and other libraries.
- XXE Configuration Review: Verify secure feature settings across five XML parsers (DocumentBuilderFactory, SAXParser, XMLInputFactory, TransformerFactory, SchemaFactory) and analyze input sources and echo behavior.
- SSTI Detection: Check Velocity, FreeMarker, and Thymeleaf rendering contexts for user-controlled template input and validate sandbox configurations like SecureUberspector and TemplateClassResolver.
- Use Case: During a Java application code review, use this Skill to locate every readObject() call, confirm the session cookie is user-controlled, find commons-collections 3.2.1 in the dependency tree, and produce EVID-formatted evidence rated Critical.
Quick Start
Audit this Java project for deserialization, XXE, and SSTI vulnerabilities and report findings with evidence.