kandi X-RAY | debugAgent Summary
kandi X-RAY | debugAgent Summary
Custom java agent for production debugging as presented by Tal Weiss from Takipi @ JavaOne '14 SF.
Top functions reviewed by kandi - BETA
- Overrides superclass method
- Resizes the instructions of this method
- Merges the input frame of this basic block with the given basic block
- Processes a stack frame
- Visits the annotation
- Adds a new constant pool to the constant pool
- Puts a string into the byte array
- Encodes a UTF8 string into a byte vector
- Processes the catch block
- Processes a parameter annotation
- Copy constant pool data to the given class writer
- Processes a jump instruction
- Processes a var instruction
- Load a LDC instruction
- Visit a local variable annotation
- Processes a method instruction
- Converts a string path to a TypePath object
- Processes a field instruction
- Returns a string representation of this type path
- Returns a string representation of the aggregate
- Main method for testing purposes
- Generate an invokeynamic instruction
- Create the class visitor
- Load an annotation
- Visits a lookup switch instruction
- Returns a string representation of the stack
debugAgent Key Features
debugAgent Examples and Code Snippets
Trending Discussions on Security Testing
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...
ANSWERAnswered 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.
No vulnerabilities reported
You can use debugAgent 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 debugAgent 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 .
Reuse Trending Solutions
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page