Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
JNDI-Injection-Exploit-Plus Alternatives
Similar projects and alternatives to JNDI-Injection-Exploit-Plus based on common topics and language
-
ysoserial
A proof-of-concept tool for generating payloads that exploit unsafe Java object deserialization.
-
JNDI-Exploit-Kit
JNDI-Exploitation-Kit(A modified version of the great JNDI-Injection-Exploit created by @welk1n. This tool can be used to start an HTTP Server, RMI Server and LDAP Server to exploit java web apps vulnerable to JNDI Injection)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
AndroRAT
A Simple android remote administration tool using sockets. It uses java on the client side and python on the server side
-
JNDIExploit
一款用于JNDI注入利用的工具,大量参考/引用了Rogue JNDI项目的代码,支持直接植入内存shell,并集成了常见的bypass 高版本JDK的方式,适用于与自动化工具配合使用。 (by 0x727)
-
RmiTaste
RmiTaste allows security professionals to detect, enumerate, interact and exploit RMI services by calling remote methods with gadgets from ysoserial.
JNDI-Injection-Exploit-Plus reviews and mentions
- JNDI-Injection-Exploit-Plus tool for generating workable JNDI links and provide background services by starting RMI server,LDAP server and HTTP server.
- GitHub - cckuailong/JNDI-Injection-Exploit-Plus: 80+ Gadgets(30 More than ysoserial). JNDI-Injection-Exploit-Plus is a tool for generating workable JNDI links and provide background services by starting RMI server,LDAP server and HTTP server.
-
Java deserialization payloads in log4j (Unified starting point)
So I've finished the unified box in stage 2 of the starting point and have tons of questions about the box. In the box they use veracode-research/rogue-jndi to exploit the log4j vulnerability. But when I test it with deserialize payload generated by frohoff/ysoserial it's not running. I've try to look at the java log in the challenge container but can't find anything that java complain or error out. Is it because the ysoserial payload too complex that it running but fail at some point and don't throw error or maybe the author just hard code so that only the payload from rogue-jndi work? can it's because of the java version/framework/library/weirdness? Do I need to test both kind of payload if I want to exploit log4j in the future or just stick with pimps/JNDI-Expoit-Kit or cckuailong/JNDI-Injection_Exploit-Plus (my senior recommendation when exploiting log4j).
-
A note from our sponsor - InfluxDB
www.influxdata.com | 1 May 2024
Stats
cckuailong/JNDI-Injection-Exploit-Plus is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of JNDI-Injection-Exploit-Plus is Java.
Sponsored