Skip to content

Releases: epi052/feroxbuster

v1.1.1

23 Oct 12:20
c85cf21

Choose a tag to compare

  • Adds a version check when the binary is executed.

When the user's version is out of sync with the latest release, an additional line is added to the banner (shown below).

 🎉  New Version Available │ https://github.com/epi052/feroxbuster/releases/latest
───────────────────────────┴──────────────────────

v1.1.0

22 Oct 11:34
952f44e

Choose a tag to compare

  • Added ability to extract links from response bodies

Extract Links Feature Description

Search through the body of valid responses (html, javascript, etc...) for additional endpoints to scan. This turns
feroxbuster into a hybrid that looks for both linked and unlinked content.

Example request/response with --extract-links enabled:

  • Make request to http://example.com/index.html
  • Receive, and read in, the body of the response
  • Search the body for absolute and relative links (i.e. homepage/assets/img/icons/handshake.svg)
  • Add the following directories for recursive scanning:
    • http://example.com/homepage
    • http://example.com/homepage/assets
    • http://example.com/homepage/assets/img
    • http://example.com/homepage/assets/img/icons
  • Make a single request to http://example.com/homepage/assets/img/icons/handshake.svg
./feroxbuster -u http://127.1 --extract-links

v1.0.5

17 Oct 17:58

Choose a tag to compare

  • Fixed issue where wordlists with comments / empty lines were still being processed as words.

Thanks to Hack The Box user @sparkla for the feedback! Original discussion is here

v1.0.4

12 Oct 12:22
185808b

Choose a tag to compare

While helping github user @Flangyver troubleshoot the bug that was fixed in v1.0.3, we realized that log records couldn't actually be redirected to a file (this is due to the progress bar library's expected behavior). This version addresses that shortcoming.

  • -v enabled logging can be saved to a file by also using -o
    • -v logging can NOT be redirected using >, |, etc...

Example:

./feroxbuster -u http://example.com -o trace.log -vvvv

v1.0.3

09 Oct 02:08
71649d1

Choose a tag to compare

  • fixed instances of duplicate scans during recursion
    • in certain situations a scan against http://example.com and http://example.com/ could both be running at the same time (the same goes for any sub-directory found during recursion

Special thanks to github user @Flangyver for notifying me about the bug ❤️

v1.0.2

07 Oct 23:07

Choose a tag to compare

  • altered request timeouts to be logged as warnings instead of errors
    • timeouts can still be viewed with 1 or more -v's as part of the command
    • all other errors encountered during a request remain errors

v1.0.1

06 Oct 00:44

Choose a tag to compare

  • fixed an issue that could present itself when join was called more than once
    • instead of relying on directory depth to determine whether to call .join or not, an AtomicUsize is checked instead

Thanks to twitter user @BoDresha for reaching out and letting me know about the bug!

v1.0.0

04 Oct 15:30

Choose a tag to compare

🥳 First major release 🥳

v0.2.1

03 Oct 15:17

Choose a tag to compare

v0.2.1 Pre-release
Pre-release
  • added /etc/feroxbuster as a valid config location
  • updated .deb to install the example config at /etc/feroxbuster
  • updated .deb to respect /etc/feroxbuster/ferox-config.toml as a conffile

v0.2.0

03 Oct 13:21

Choose a tag to compare

v0.2.0 Pre-release
Pre-release
  • config file is now searched for in multiple locations
    • ~/.config/feroxbuster
    • same dir as feroxbuster
    • cwd
  • added some better error messaging
  • updated docs/readme to reflect changes to config management
  • updated .deb to respect a config file found at ~/.config/feroxbuster