Releases: epi052/feroxbuster
v1.1.1
- 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
- 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
bodyof the response - Search the
bodyfor absolute and relative links (i.e.homepage/assets/img/icons/handshake.svg) - Add the following directories for recursive scanning:
http://example.com/homepagehttp://example.com/homepage/assetshttp://example.com/homepage/assets/imghttp://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
v1.0.4
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.
-venabled logging can be saved to a file by also using-o-vlogging can NOT be redirected using>,|, etc...
Example:
./feroxbuster -u http://example.com -o trace.log -vvvv
v1.0.3
- fixed instances of duplicate scans during recursion
- in certain situations a scan against
http://example.comandhttp://example.com/could both be running at the same time (the same goes for any sub-directory found during recursion
- in certain situations a scan against
Special thanks to github user @Flangyver for notifying me about the bug ❤️
v1.0.2
v1.0.1
- 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
v0.2.1
v0.2.0
- 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