wfuzz | Web application fuzzer | Security Testing library

by xmendez Python Version: v3.1.0 License: GPL-2.0

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

kandi X-RAY | wfuzz Summary

wfuzz is a Python library typically used in Testing, Security Testing applications. wfuzz has no bugs, it has no vulnerabilities, it has build file available, it has a Strong Copyleft License and it has medium support. You can download it from GitHub.

Wfuzz has been created to facilitate the task in web applications assessments and it is based on a simple concept: it replaces any reference to the FUZZ keyword by the value of a given payload. A payload in Wfuzz is a source of data. This simple concept allows any input to be injected in any field of an HTTP request, allowing to perform complex web security attacks in different web application components such as: parameters, authentication, forms, directories/files, headers, etc.

Support

Quality

Security

License

Reuse

Support

wfuzz has a medium active ecosystem.

It has 5079 star(s) with 1310 fork(s). There are 164 watchers for this library.

It had no major release in the last 12 months.

There are 62 open issues and 124 have been closed. On average issues are closed in 153 days. There are 28 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of wfuzz is v3.1.0

Quality

wfuzz has 0 bugs and 0 code smells.

Security

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

wfuzz code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

wfuzz is licensed under the GPL-2.0 License. This license is Strong Copyleft.

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

Reuse

wfuzz releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

wfuzz saves you 6518 person hours of effort in developing the same functionality from scratch.

It has 13546 lines of code, 1090 functions and 139 files.

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

Top functions reviewed by kandi - BETA

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

Compile the feed
Compile the dictio
Compile the seeds
Create a FuzzStats object from the options dict
Parse command line arguments
Check if options are incompatible
Parse proxy options
Parse filter options
Returns True if res is visible False otherwise
Replaces markers in FPM
Perform search
Get terminal size
Returns the next word from the feed
Process a fuzz response
Set url
Process a fuzzed response
Computes the fuzz value for the given token
Computes fuzz value for given match dict
Process results
Open file with encoding
Convert a pycurl request into a Python object
Start the GUI
Main thread
Print header of summary
Read all curl objects
Print result

Get all kandi verified functions for this library.

wfuzz Key Features

No Key Features are available at this moment for wfuzz.

wfuzz Examples and Code Snippets

cfuzz,Usage,Filter results

Lines of Code : 12

License : Permissive (Unlicense)

Copy

  -omin, --stdout-min         filter to only display if stdout characters number is lesser than n
  -omax, --stdout-max         filter to only display if stdout characters number is greater than n
  -oeq,  --stdout-equal       filter to only display

Package Groups

Shell

Lines of Code : 12

License : Non-SPDX (NOASSERTION)

Copy

# pacman -S blackarchlinux-intel

# pacman -S blackarchlinux-forensics

# pacman -S blackarchlinux-exploitation

# pacman -S blackarchlinux-defensive

# pacman -S blackarchlinux-wireless

# pacman -S blackarchlinux-analysis

# pacman -S blackarchlinu

Docker Image Generator,Examples

Lines of Code : 10

License : Permissive (MIT)

Copy

    docker run -it --rm mytools
    root@dff16ee1f45c:/opt#

    docker run -it --rm mytools nmap localhost
    
    Starting Nmap 7.60 ( https://nmap.org ) at 2020-04-10 21:35 UTC
    Nmap scan report for localhost (127.0.0.1)
    ...

    ./doig -i

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