fuzzdb | attack patterns and primitives for black-box application | Security Testing library

by fuzzdb-project PHP Version: Current License: No License

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

kandi X-RAY | fuzzdb Summary

fuzzdb is a PHP library typically used in Testing, Security Testing applications. fuzzdb has no bugs, it has no vulnerabilities and it has medium support. You can download it from GitHub.

fuzzdb was created to increase the likelihood of finding application security vulnerabilities through dynamic application security testing. it's the first and most comprehensive open dictionary of fault injection patterns, predictable resource locations, and regex for matching server responses. attack patterns - fuzzdb contains comprehensive lists of attack payload primitives for fault injection testing. these patterns, categorized by attack and where appropriate platform type, are known to cause issues like os command injection, directory listings, directory traversals, source exposure, file upload bypass, authentication bypass, xss, http header crlf injections, sql injection, nosql injection, and more. for example, fuzzdb catalogs 56 patterns that can potentially be interpreted as a null byte and contains lists of commonly used methods such as "get, put, test," and name-value pairs than trigger debug modes. discovery - the popularity of standard

Support

Quality

Security

License

Reuse

Support

fuzzdb has a medium active ecosystem.

It has 7455 star(s) with 2077 fork(s). There are 367 watchers for this library.

It had no major release in the last 6 months.

There are 5 open issues and 148 have been closed. On average issues are closed in 449 days. There are 10 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of fuzzdb is current.

Quality

fuzzdb has 0 bugs and 0 code smells.

Security

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

fuzzdb code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

fuzzdb does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

fuzzdb releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of fuzzdb

Get all kandi verified functions for this library.

fuzzdb Key Features

No Key Features are available at this moment for fuzzdb.

fuzzdb Examples and Code Snippets

No Code Snippets are available at this moment for fuzzdb.

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 fuzzdb

While in the FuzzDB dir, you can update your local repo with the command. This Stackoverflow gives ideas on how to keep a local repository tidy: https://stackoverflow.com/questions/38171899/how-to-reduce-the-depth-of-an-existing-git-clone/46004595#46004595. You can also browse the FuzzDB github sources and there is always a fresh zip file. Note: Some antivirus/antimalware software will alert on FuzzDB. To resolve, the filepath should be whitelisted. There is nothing in FuzzDB that can harm your computer as-is, however due to the risk of local file include attacks it's not recommended to store this repository on a server or other important system. Use at your own risk.

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: