JNDI-Injection-Exploit | generates JNDI links can start several servers | Security Testing library

by welk1n Java Version: v1.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | JNDI-Injection-Exploit Summary

JNDI-Injection-Exploit is a Java library typically used in Testing, Security Testing, Docker applications. JNDI-Injection-Exploit has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has medium support. You can download it from GitHub.

JNDI-Injection-Exploit is a tool for generating workable JNDI links and provide background services by starting RMI server,LDAP server and HTTP server. RMI server and LDAP server are based on marshals and modified further to link with HTTP server. Using this tool allows you get JNDI links, you can insert these links into your POC to test vulnerability.

Support

Quality

Security

License

Reuse

Support

JNDI-Injection-Exploit has a medium active ecosystem.

It has 2228 star(s) with 707 fork(s). There are 26 watchers for this library.

It had no major release in the last 12 months.

There are 5 open issues and 3 have been closed. On average issues are closed in 33 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of JNDI-Injection-Exploit is v1.0

Quality

JNDI-Injection-Exploit has 0 bugs and 0 code smells.

Security

JNDI-Injection-Exploit has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

JNDI-Injection-Exploit code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

JNDI-Injection-Exploit is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

JNDI-Injection-Exploit releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

JNDI-Injection-Exploit saves you 355 person hours of effort in developing the same functionality from scratch.

It has 849 lines of code, 45 functions and 11 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed JNDI-Injection-Exploit and discovered the below as its top functions. This is intended to give you an instant insight into JNDI-Injection-Exploit implemented functionality, and help decide if they suit your requirements.

Main method for testing
The command line options
Checks if the current operating system is Linux
Add the given string to the given string
Entry point
Convenience method
Main loop
Handle RMI
Wait for a connection
Get current time
Get the first constructor with the given name
Close the sink
Insert a command into a byte array
Gets local IP
Start the download servlet
Check the filename of a template
Create dummy object
Main entry point
Gets the value of an object field

Get all kandi verified functions for this library.

JNDI-Injection-Exploit Key Features

No Key Features are available at this moment for JNDI-Injection-Exploit.

JNDI-Injection-Exploit Examples and Code Snippets

No Code Snippets are available at this moment for JNDI-Injection-Exploit.

Community Discussions

Trending Discussions on Security Testing

DAST security scaning of a IoT Nodemcu esp8266 LUA script www HTML server connected to camera and A/C relay

QUESTION

DAST security scaning of a IoT Nodemcu esp8266 LUA script www HTML server connected to camera and A/C relay

Asked 2021-Apr-08 at 01:04

I have not, but shall DAST* security test, out of curiosity, an IoT device; Nodemcu esp8266 www server I built. It's showing a HTML page (on a mobile phone for example) that allows to control and interact with a camera module and a A/C relay. With it I can for example show images captured in the camera I even think it has some image recognition built in, and I can switch on and off a relay for electrical current to a light bulb (110/220v A/C power)

Before I start pentest I though I better start thinking of what types of exploits one would be able to find and detect? Which sinister exploits I will be able to find, or rather ought be able to find given a proper pentest exercise? (And if I do not find exploits, my approach to the pentest of the Iot might be wrong)

I ponder it might be a totally pointless exercise since the esp8266 www server (or rather its LUA programming libraries) might not have any security built into it, so basically it is "open doors" and everything with it is unsafe ?

The test report might just conclude what I can foresee be that the the "user input needs to be sanitized"?

Anyone have any idea what such pentest of a generic IoT device generally reports? Maybe it is possible to crash or reset the IoT device? Buffer overruns, XXS, call own code ?

I might use ZAP or Burpsuite or similar DAST security test tool.

I could of course SAST test it instead, or too, but I think it will be hard to find a static code analyzer for the NodeMCU libraries and NUA scripting language easily ? I found some references here though: https://ieeexplore.ieee.org/abstract/document/8227299 but it seems to be a long read.

So if someone just have a short answer what to expect in a DAST scan/pentest , it would be much appreciated.

Stay safe and secure out there ! Zombieboy

...

ANSWER

Answered 2021-Apr-08 at 01:04

I do my vulnerability scanning with OpenVAS (I assume this is what you mean by pentesting?). I am not aware of any IOT focused Tools.

If your server is running on esp8266, i would imagine that there is no much room for authentication and encryption of http traffic, but correct me if i am wrong).

Vulnerability Scan results might show things like unencrypted http traffic, credentials transmitted in cleartext (if you have any credentials fields in the pages served by the web server) etc. Depending on if there is encryption, you might also see weak encryption findings.

You might get some false positives on your lua webserver reacting like other known webservers when exploits are applied. I have seen this kind of false positive specially on DoS vulnerabilities when a vulnerability scan is testing a vulnerability and the server becomes unresponsive. Depending on how invasive your vulnerability scanner is, you might get a lot of false positives for DoS on such a constrained platform.

Source https://stackoverflow.com/questions/66995125

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install JNDI-Injection-Exploit

We can select one of the two methods to get the jar.
Download the latest jar from Realease.
Clone the source code to local and build (Requires Java 1.8+ and Maven 3.x+). $ git clone https://github.com/welk1n/JNDI-Injection-Exploit.git $ cd JNDI-Injection-Exploit $ mvn clean package -DskipTests

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: