Burp-IndicatorsOfVulnerability | Burp extension that checks application requests | Security Testing library

by codewatchorg Java Version: Current License: BSD-2-Clause

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

kandi X-RAY | Burp-IndicatorsOfVulnerability Summary

Burp-IndicatorsOfVulnerability is a Java library typically used in Testing, Security Testing applications. Burp-IndicatorsOfVulnerability has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

The extension checks the following things: 1. Application response bodies for specific strings that indicate a vulnerability is present, such as error output indicative of SQLi, Serialization issues, XXE issues, etc, and 2. Application requests in the URL and Body for potential targets of SSRF/LFI/RFI/Directory Traversal/URL Injection attack. 3. Application requests and responses in URLs, bodies, and headers for AWS S3 buckets/Azure Storage containers/Google storage containers. 4. Application requests for parameters that might indicate targets for other common attack vectors (similar to HUNT). 5. Application responses for potential leaking of secrets.

Support

Quality

Security

License

Reuse

Support

Burp-IndicatorsOfVulnerability has a low active ecosystem.

It has 35 star(s) with 9 fork(s). There are 7 watchers for this library.

It had no major release in the last 6 months.

Burp-IndicatorsOfVulnerability has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of Burp-IndicatorsOfVulnerability is current.

Quality

Burp-IndicatorsOfVulnerability has 0 bugs and 0 code smells.

Security

Burp-IndicatorsOfVulnerability has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Burp-IndicatorsOfVulnerability code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Burp-IndicatorsOfVulnerability is licensed under the BSD-2-Clause License. This license is Permissive.

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

Reuse

Burp-IndicatorsOfVulnerability 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.

Top functions reviewed by kandi - BETA

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

Process the HTTP message
This method creates the scan issues
Search for matches in the response string
Registers the extensions
Prints the alert header to the console
Scanner for the request
Generates random string
Performs a passive scan for a given message
This method determines if the given issue has duplicate issues

Get all kandi verified functions for this library.

Burp-IndicatorsOfVulnerability Key Features

No Key Features are available at this moment for Burp-IndicatorsOfVulnerability.

Burp-IndicatorsOfVulnerability Examples and Code Snippets

No Code Snippets are available at this moment for Burp-IndicatorsOfVulnerability.

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 Burp-IndicatorsOfVulnerability

You can download it from GitHub.
You can use Burp-IndicatorsOfVulnerability 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 Burp-IndicatorsOfVulnerability 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: