omapi-cve-2015-6606-exploit | Simple Exploit for Verification of CVE-2015-6606 | Security Testing library

by michaelroland Java Version: Current License: GPL-3.0

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

kandi X-RAY | omapi-cve-2015-6606-exploit Summary

omapi-cve-2015-6606-exploit is a Java library typically used in Testing, Security Testing applications. omapi-cve-2015-6606-exploit has no bugs, it has no vulnerabilities, it has build file available, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

Simple Exploit for Verification of CVE-2015-6606

Support

Quality

Security

License

Reuse

Support

omapi-cve-2015-6606-exploit has a low active ecosystem.

It has 3 star(s) with 2 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

omapi-cve-2015-6606-exploit has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of omapi-cve-2015-6606-exploit is current.

Quality

omapi-cve-2015-6606-exploit has no bugs reported.

Security

omapi-cve-2015-6606-exploit has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

omapi-cve-2015-6606-exploit is licensed under the GPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

omapi-cve-2015-6606-exploit 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 omapi-cve-2015-6606-exploit and discovered the below as its top functions. This is intended to give you an instant insight into omapi-cve-2015-6606-exploit implemented functionality, and help decide if they suit your requirements.

Invoked when a menu button is clicked
This method is used for debugging
Dump the contents of this element to a PrintStream
Dumps information about the current context
Get the process name associated with the given PID
Inflates the menu menu
This method is called when the menu item is selected
Inflates menu item menu
Sets the activity to be saved
Override this method to handle back button selection
Sets the text from the main view
Set the activity s state
Allow reinvoke
Resume context info
Initializes the activity
Called when an option is selected
Checks if the given name starts with one of the given prefixes

Get all kandi verified functions for this library.

omapi-cve-2015-6606-exploit Key Features

No Key Features are available at this moment for omapi-cve-2015-6606-exploit.

omapi-cve-2015-6606-exploit Examples and Code Snippets

No Code Snippets are available at this moment for omapi-cve-2015-6606-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 omapi-cve-2015-6606-exploit

You can download it from GitHub.
You can use omapi-cve-2015-6606-exploit 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 omapi-cve-2015-6606-exploit 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: