BloodHound.py | A Python based ingestor for BloodHound | Security Testing library
kandi X-RAY | BloodHound.py Summary
kandi X-RAY | BloodHound.py Summary
BloodHound.py is a Python based ingestor for BloodHound, based on Impacket. This version of BloodHound.py is only compatible with BloodHound 4.1 or newer. For the 3.x range, use version 1.1.1 via pypi.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Query the domain controller
- Dump a struct
- Return a hexadecimal representation of a string
- Resolve collection methods
- Run a worker process
- Enumerate a list of computers
- Returns a list of domains
- Load the cached DNs from a cachefile
- Read the contents of the struct
- Read bits from the stream
- Resets the buffer
- Get trusted domains
- Connects to the domain controller
- Write to stream
- Loads a cstruct file
- Lookup GO IDs for a given SAM name
- Resolve a sid entry
- Set kerberos credential cache
- Parses a task xml
- Serialize the given data into a byte string
- Write data to stream
- Work on processes
- Load a file
- Load a cstruct file
- Return the contents of a file
- Read from the stream
- Read the first value from the stream
BloodHound.py Key Features
BloodHound.py Examples and Code Snippets
Community Discussions
Trending Discussions on Security Testing
QUESTION
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:04I 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.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install BloodHound.py
Default - Performs group membership collection, domain trust collection, local admin collection, and session collection
Group - Performs group membership collection
LocalAdmin - Performs local admin collection
RDP - Performs Remote Desktop Users collection
DCOM - Performs Distributed COM Users collection
PSRemote - Performs Remote Management (PS Remoting) Users collection
DCOnly - Runs all collection methods that can be queried from the DC only, no connection to member hosts/servers needed. This is equal to Group,Acl,Trusts,ObjectProps
Session - Performs session collection
Acl - Performs ACL collection
Trusts - Performs domain trust enumeration
LoggedOn - Performs privileged Session enumeration (requires local admin on the target)
ObjectProps - Performs Object Properties collection for properties such as LastLogon or PwdLastSet
All - Runs all methods above, except LoggedOn
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page