java-exploit-chain

Assemble Java audit findings into validated multi-vulnerability exploit chains with severity scoring.

1.7k|238|Updated Dec 7, 2019
One-click install
npx skills add https://github.com/wgpsec/AboutSecurity --skill java-exploit-chain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java-exploit-chain
Source: https://github.com/wgpsec/AboutSecurity/tree/main/skills/code-audit/java/java-exploit-chain
Command: npx skills add https://github.com/wgpsec/AboutSecurity --skill java-exploit-chain

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Individual medium or low-severity findings from a Java white-box audit often look harmless in isolation, but combining them can produce Critical-level attack paths. This Skill provides a structured methodology for chaining discovered vulnerabilities, auditing Maven/Gradle dependencies for exploitable CVEs, and analyzing deserialization gadget chains so audit results reflect real-world impact.

Core Features & Use Cases

  • Three-Stage Chain Assembly: Classify findings into INFO, AUTH, and EXEC stages, then validate that each stage's output satisfies the next stage's preconditions with evidence (EVID) requirements.
  • Dependency CVE Auditing: Extract Maven/Gradle dependency trees, cross-reference NVD and GitHub Advisory, and apply a three-step exploitability check (version match, reachable code path, exposed attack surface).
  • Gadget Chain Analysis: Match classpath dependencies against ysoserial payloads, plan marshalsec JNDI exploitation with JDK version constraints, and discover custom gadgets in project code.
  • Use Case: During a Spring Boot audit you find an exposed Actuator endpoint and JWT authentication. Use this Skill to chain information disclosure to JWT forgery to admin RCE, then score the chain with the feasibility coefficient formula.

Quick Start

Analyze the vulnerabilities found in my Java audit and assemble them into scored exploit chains with evidence for each step.

Frequently Asked Questions about java-exploit-chain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I combine multiple Java vulnerabilities into an exploit chain?

Classify each finding into INFO, AUTH, or EXEC stages, then verify that each stage's output satisfies the next stage's preconditions with concrete evidence such as code locations and data flow. Score the chain by multiplying the final effect severity by a feasibility coefficient between 0.6 and 1.0.

How to check if a Maven dependency CVE is actually exploitable?

Apply a three-step verification: confirm the project version falls within the CVE's affected range, trace whether the vulnerable code path is actually called by the project, and check whether the entry point is exposed to attackers. A CVE that fails any step is marked present but not exploitable.

Which ysoserial gadget chain should I use for a target?

Scan the target classpath from pom.xml, build.gradle, or WEB-INF/lib to identify available libraries and versions, then select the matching chain such as CommonsCollections6 for commons-collections 3.1 or CommonsBeanutils1 for commons-beanutils. The reference tables map dependencies to chains and their trigger effects.

Does JNDI remote class loading work on newer JDK versions?

RMI remote class loading is disabled by default from JDK 8u121, and LDAP from 8u191 onward. On newer versions, use bypasses such as local class gadgets like Tomcat BeanFactory, LDAP-returned serialized data with an existing classpath gadget, or Groovy-based payloads.

What are the limitations of white-box exploit chain analysis?

This methodology validates chain feasibility at the source code level only; constructing remote exploits, sending payloads, and bypassing WAFs belong to separate black-box exploitation skills. Chains with strong environment dependencies receive lower feasibility coefficients and require documented fallback paths.