feroxbuster: [BUG] Feroxbuster crashes when trying to resume from state file
Describe the bug
I tried on two different machines and I get same result. I take original cmdline and change -u to --resume-from and give it a state file as an arguments. It starts “normally” I see urls parsed, etc. but after that I get this:
thread ‘tokio-runtime-worker’ panicked at ‘range start index 206257 out of range for slice of length 107983’, src/event_handlers/scans.rs:302:33
note: run with RUST_BACKTRACE=1
environment variable to display a backtrace
Aborted
with RUST_BACKTRACE=1 I get:
thread ‘tokio-runtime-worker’ panicked at ‘range start index 206257 out of range for slice of length 107983’, src/event_handlers/scans.rs:302:33
stack backtrace:
note: Some details are omitted, run with RUST_BACKTRACE=full
for a verbose backtrace.
Aborted
301 GET 7l 20w 244c https://example.com/flv => http://example.com/flv/
301 GET 7l 20w 248c https://example.com/ads => http://example.com/ads/
301 GET 7l 20w 243c https://example.com/ps => http://example.com/ps/
[####################] - 0s 1142938/0 0s
thread ‘tokio-runtime-worker’ panicked at ‘range start index 206257 out of range for slice of length 107983’, src/event_handlers/scans.rs:302:33
stack backtrace:
0: 0x7f580f7ea42c - <unknown>
1: 0x7f580f5640be - <unknown>
2: 0x7f580f7bd7f4 - <unknown>
3: 0x7f580f7eb9ef - <unknown>
4: 0x7f580f7eb5ef - <unknown>
5: 0x7f580f7ec672 - <unknown>
6: 0x7f580f7ec154 - <unknown>
7: 0x7f580f7ec0bc - <unknown>
8: 0x7f580f7ec091 - <unknown>
9: 0x7f580f4be802 - <unknown>
10: 0x7f580f562fa1 - <unknown>
11: 0x7f580f4be896 - <unknown>
12: 0x7f580f6194ab - <unknown>
13: 0x7f580f617765 - <unknown>
14: 0x7f580f613bfe - <unknown>
15: 0x7f580f6125a6 - <unknown>
16: 0x7f580f7f93a5 - <unknown>
17: 0x7f580f7fc9bc - <unknown>
18: 0x7f580f7f137a - <unknown>
19: 0x7f580f7f1108 - <unknown>
20: 0x7f580f7edab5 - <unknown>
Aborted
I pasted little more data for context 😃
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 31 (16 by maintainers)
I just replaced all occurrences of :1619745 with :107982 (your math was correct) and it looks to be working fine. I have one more question does feroxbuster retry requests to which it receives 429 status code ?