jndi-injection

The Skill detects JNDI injection vulnerabilities by analyzing RMI, LDAP, and DNS lookup patterns in your Java application to identify when attacker-controlled names are used. Run 'jndi-injection scan my-app.jar' to check your codebase.

JNDI injection attack vectors exploit RMI, LDAP, and DNS protocols by injecting attacker-controlled names into JNDI lookups. The Skill analyzes these lookup patterns to identify which specific protocol vectors your Java application is vulnerable to.

Yes, testing JNDI injection requires Java and tools like marshalsec and JNDI-Injection-Exploit for scanning and exploitation. These dependencies enable you to run a JNDI reference server and validate vulnerabilities in your application.

JDK version constraints impact JNDI injection by restricting remote class loading in newer versions, requiring specific bypass methods. The Skill details these constraints and bypass techniques, including the impact of Log4Shell (CVE-2021-44228) on vulnerable JDK versions.

The best way to test JNDI injection vulnerabilities is by using a JNDI reference server tool like marshalsec to simulate attacks. The Skill provides a structured testing methodology to validate RMI, LDAP, and DNS attack vectors against your Java application.

Yes, the Skill can scan Java frameworks like Spring and Log4j2 for JNDI lookup issues. It identifies when these frameworks perform JNDI lookups with attacker-controlled names and assesses the associated vulnerability risks.