o365spray | Username enumeration and password spraying tool | Security Testing library

by 0xZDH Python Version: Current License: MIT

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

kandi X-RAY | o365spray Summary

o365spray is a Python library typically used in Testing, Security Testing applications. o365spray 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.

This is a username enumeration and password spraying tool aimed at Microsoft O365. For educational purposes only. This tool reimplements a collection of enumeration and spray techniques researched and identified by those mentioned in Acknowledgments. WARNING: ActiveSync user enumeration is performed by submitting a single authentication attempt per user. If ActiveSync enumeration is run with password spraying, the tool will automatically reset the lockout timer prior to the password spray -- if enumeration is run alone, the user should be aware of the authentication attempts and reset the lockout timer manually. OneDrive user enumeration relies on the target user(s) to have previously logged into OneDrive. If a valid user has not yet used OneDrive, their account will show as 'invalid'. This appears to be a viable solution for user enumeration against federated realms.

Support

Quality

Security

License

Reuse

Support

o365spray has a low active ecosystem.

It has 519 star(s) with 78 fork(s). There are 8 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 7 have been closed. On average issues are closed in 129 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of o365spray is current.

Quality

o365spray has 0 bugs and 0 code smells.

Security

o365spray has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

o365spray code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

o365spray is licensed under the MIT License. This license is Permissive.

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

Reuse

o365spray 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.

Installation instructions are not available. Examples and code snippets are available.

o365spray saves you 368 person hours of effort in developing the same functionality from scratch.

It has 1691 lines of code, 60 functions and 18 files.

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

Top functions reviewed by kandi - BETA

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

Enumerate users
Send a HTTP request
Shutdown the writer
Ensure the user is valid
Add Forwarded - Forwarded headers
Generate a random forwarded address
Generate a random API id
Generate an AMzn Trace ID
Ping a user
Check the response
Shutdown the connection
Validate a domain
Validate domain
Spay a user
Enumerate a domain
Spay a domain
Sends an email
Send an email to FireProx
Validate the given domain
Write credentials to file
Parse command line arguments
Says the given domain and password
Enumerate a user
Sprays an enum

Get all kandi verified functions for this library.

o365spray Key Features

No Key Features are available at this moment for o365spray.

o365spray Examples and Code Snippets

No Code Snippets are available at this moment for o365spray.

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 o365spray

You can download it from GitHub.
You can use o365spray like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

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: