jndi-injection

JNDI injection targets the Java Naming and Directory Interface lookup mechanism with attacker-controlled names to load remote classes via RMI or LDAP, which is a distinct attack surface from base deserialization vulnerabilities despite sharing similar gadget chains.

Log4Shell bypass involves using detection payloads and WAF evasion variants that abuse JNDI lookups via RMI, LDAP, or DNS, often requiring tools like marshalsec or Rogue JNDI to serve malicious classes to the vulnerable Java application.

Yes, marshalsec and ysoserial are required dependencies for JNDI injection exploitation, providing the necessary gadget chains and rogue directory services to achieve remote code execution through RMI, LDAP, and post-8u191 bypass vectors.

JDK version constraints restrict direct remote class loading via RMI and LDAP in Java versions post-8u191, requiring attackers to bypass these limitations using deserialization gadgets from ysoserial to achieve remote code execution.

Yes, JNDI-Injection-Exploit and Rogue JNDI support RMI, LDAP, and DNS vectors for testing JNDI injection, providing WAF bypass variants and detection payloads to validate vulnerabilities in Java applications.