jndiat | JNDI Attacking Tool ) is an open source penetration | Security Testing library

by quentinhardy Java Version: v2.0 License: No License

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

kandi X-RAY | jndiat Summary

jndiat is a Java library typically used in Testing, Security Testing applications. jndiat has no bugs, it has no vulnerabilities and it has low support. However jndiat build file is not available. You can download it from GitHub.

JNDIAT (JNDI Attacking Tool) is an open source penetration testing tool that tests the security of Weblogic servers through T3 protocol. Usage examples of JNDIAT: * You want to search if there are Weblogic ports which are accessible through T3 protocol; * You want to search valid accounts remotely in order to have a privileged connection; * You want to list JNDIs (Java Naming and Directory Interface) which are accessible to know what you can do on the remote Weblogic server (without or with a Weblogic account); * You want to use a unprotected (i.e. 'public') JDBC datasource in order to get a remote interactive SQL shell; * You want to deploy an application (e.g. War) on the Weblogic server in order to have a Web shell (account required). Tested on Oracle Weblogic 11.

Support

Quality

Security

License

Reuse

Support

jndiat has a low active ecosystem.

It has 219 star(s) with 48 fork(s). There are 8 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 1 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of jndiat is v2.0

Quality

jndiat has 0 bugs and 0 code smells.

Security

jndiat has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jndiat code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jndiat does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

jndiat releases are available to install and integrate.

jndiat has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

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

Gets the SQL shell
Print rows of a ResultSet to standard out
Generate SQL shell for the SQL command
Initialize the connection
Display application list
Store the remote server
Gets the remote deployment manager
Create a new keystore in the keystore
Deploys an application file
Sleep milliseconds
Try to start an application
Finds the best TargetModuleID for a given application
Undeploys an application to the remote server
Undeploys an application name
Tries to stop an application by its name
Listen to SQL
Converts the ResultSet to an XML document
Ask the user to choose a datasource to use
Get the datasources
Get all possible ME names
Search for valid credentials
Scan the given IP address
Prints valid credentials
Returns the ModuleType from the extension
Add common options

Get all kandi verified functions for this library.

jndiat Key Features

No Key Features are available at this moment for jndiat.

jndiat Examples and Code Snippets

No Code Snippets are available at this moment for jndiat.

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 jndiat

You can download it from GitHub.
You can use jndiat like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the jndiat component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

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: