burp-co2 | A collection of enhancements for Portswigger | Security Testing library

by JGillam Java Version: 1.1.13 License: Non-SPDX

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

kandi X-RAY | burp-co2 Summary

burp-co2 is a Java library typically used in Testing, Security Testing applications. burp-co2 has no bugs, it has no vulnerabilities, it has build file available and it has low support. However burp-co2 has a Non-SPDX License. You can download it from GitHub.

A collection of enhancements for Portswigger's popular Burp Suite web penetration testing tool.

Support

Quality

Security

License

Reuse

Support

burp-co2 has a low active ecosystem.

It has 128 star(s) with 34 fork(s). There are 11 watchers for this library.

It had no major release in the last 12 months.

There are 8 open issues and 21 have been closed. On average issues are closed in 98 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of burp-co2 is 1.1.13

Quality

burp-co2 has 0 bugs and 0 code smells.

Security

burp-co2 has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

burp-co2 code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

burp-co2 has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

burp-co2 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.

burp-co2 saves you 3214 person hours of effort in developing the same functionality from scratch.

It has 6909 lines of code, 587 functions and 108 files.

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

Top functions reviewed by kandi - BETA

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

Builds the command .
Mangle the names of the specified names .
Do the processing of the HTML tag .
Initialize UI .
Reads a list of strings from a resource file .
Checks if the given word matches this rule .
Run command .
Setup basic words popup .
Add the masher tab .
Runs the program .

Get all kandi verified functions for this library.

burp-co2 Key Features

No Key Features are available at this moment for burp-co2.

burp-co2 Examples and Code Snippets

No Code Snippets are available at this moment for burp-co2.

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-co2

This project is best built under IntelliJ IDEA. There are several modules with dependencies on other modules. Here are some key modules:. burp-api: The source is not populated by default! You must put the latest API source from Burp into this source folder before building any of the other modules. co2-core: This module contains core functionality that is used across all the CO2 modules. co2-suite: This is the full CO2 suite module. It basically depends on everything else.

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: