rogue-jndi | A malicious LDAP server for JNDI injection attacks | Security Testing library

 by   veracode-research Java Version: Current License: MIT

kandi X-RAY | rogue-jndi Summary

kandi X-RAY | rogue-jndi Summary

rogue-jndi is a Java library typically used in Testing, Security Testing, Docker applications. rogue-jndi 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.

The project contains LDAP & HTTP servers for exploiting insecure-by-default Java JNDI API. In order to perform an attack, you can start these servers locally and then trigger a JNDI resolution on the vulnerable client, e.g.:. It will initiate a connection from the vulnerable client to the local LDAP server. Then, the local server responds with a malicious entry containing one of the payloads, that can be useful to achieve a Remote Code Execution.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              rogue-jndi has a medium active ecosystem.
              It has 906 star(s) with 215 fork(s). There are 16 watchers for this library.
              OutlinedDot
              It had no major release in the last 6 months.
              There are 3 open issues and 1 have been closed. There are 4 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of rogue-jndi is current.

            kandi-Quality Quality

              rogue-jndi has 0 bugs and 0 code smells.

            kandi-Security Security

              rogue-jndi has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              rogue-jndi code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              rogue-jndi is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              rogue-jndi releases are not available. You will need to build from source code and install.
              Build file is available. You can build the component from source.
              Installation instructions are not available. Examples and code snippets are available.
              rogue-jndi saves you 248 person hours of effort in developing the same functionality from scratch.
              It has 603 lines of code, 34 functions and 17 files.
              It has low code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi has reviewed rogue-jndi and discovered the below as its top functions. This is intended to give you an instant insight into rogue-jndi implemented functionality, and help decide if they suit your requirements.
            • Send a result to the in - memory search results
            • Get a parameter value from a DN
            • Serialize an object to a byte array
            • Handles the http request
            • Send a result to the WebSphereSearch
            • Sends an LDAP result to the client
            • Sends a result to LDAP
            • Create an executable jar
            • Patches the bytecode of the specified class by injecting its execution object
            • Sends LDAP results to the given object
            • Processes a search result
            • Convert a String to a JavaScript String
            • Encode a bash script to a shell script
            Get all kandi verified functions for this library.

            rogue-jndi Key Features

            No Key Features are available at this moment for rogue-jndi.

            rogue-jndi Examples and Code Snippets

            No Code Snippets are available at this moment for rogue-jndi.

            Community Discussions

            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 rogue-jndi

            You can download it from GitHub.
            You can use rogue-jndi 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 rogue-jndi 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

            RemoteReference.java - classic JNDI attack, leads to RCE via remote classloading, works up to jdk8u191Tomcat.java - leads to RCE via unsafe reflection in org.apache.naming.factory.BeanFactoryGroovy.java - leads to RCE via unsafe reflection in org.apache.naming.factory.BeanFactory + groovy.lang.GroovyShellWebSphere1.java - leads to OOB XXE in com.ibm.ws.webservices.engine.client.ServiceFactoryWebSphere2.java - leads to RCE via classpath manipulation in com.ibm.ws.client.applicationclient.ClientJ2CCFFactory
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/veracode-research/rogue-jndi.git

          • CLI

            gh repo clone veracode-research/rogue-jndi

          • sshUrl

            git@github.com:veracode-research/rogue-jndi.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular Security Testing Libraries

            PayloadsAllTheThings

            by swisskyrepo

            sqlmap

            by sqlmapproject

            h4cker

            by The-Art-of-Hacking

            vuls

            by future-architect

            PowerSploit

            by PowerShellMafia

            Try Top Libraries by veracode-research

            spring-view-manipulation

            by veracode-researchJava

            actuator-testbed

            by veracode-researchJava

            svrwb-fuzz-benchmark-suite

            by veracode-researchC

            freebsd-perf-fuzz

            by veracode-researchC