Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reproducible segmentation fault #778

Open
berezhinskiy opened this issue May 10, 2024 · 2 comments
Open

Reproducible segmentation fault #778

berezhinskiy opened this issue May 10, 2024 · 2 comments

Comments

@berezhinskiy
Copy link

Hi, it seems there's a reproducible segmentation fault occurring.

Command:

masscan --wait=0 --open-only --interactive --config ...

Config:

rate = 5000
adapter-port = 60834-61089

ports = U:161,U:123,U:500,U:137,U:111,U:69

range = ...

Output:

Starting masscan 1.3.9-integration (http://bit.ly/14GZzcT) at 2024-05-10 13:55:21 GMT
Initiating SYN Stealth Scan
Scanning 207515 hosts [10 ports/host]

....

30 seconds later:

12: [/lib/x86_64-linux-gnu/libc.so.6(+0x129c3c) [0x7f77d1729c3c]]
?? ??:0
11: [/lib/x86_64-linux-gnu/libc.so.6(+0x9ca94) [0x7f77d169ca94]]
?? ??:0
10: [masscan(+0x19c7a) [0x5d7419ee0c7a]]
?? ??:0
9: [masscan(+0x37780) [0x5d7419efe780]]
?? ??:0
8: [masscan(+0x2d1b5) [0x5d7419ef41b5]]
?? ??:0
7: [masscan(+0x2cb36) [0x5d7419ef3b36]]
?? ??:0
6: [masscan(+0x278e4) [0x5d7419eee8e4]]
?? ??:0
5: [/lib/x86_64-linux-gnu/libc.so.6(+0x8fcb6) [0x7f77d168fcb6]]
?? ??:0
4: [/lib/x86_64-linux-gnu/libc.so.6(+0x6ad98) [0x7f77d166ad98]]
?? ??:0
3: [/lib/x86_64-linux-gnu/libc.so.6(+0x18b75d) [0x7f77d178b75d]]
?? ??:0
2: [/lib/x86_64-linux-gnu/libc.so.6(+0x45320) [0x7f77d1645320]]
?? ??:0
1: [masscan(+0x25b57) [0x5d7419eecb57]]
?? ??:0

If there's any additional info I can provide to help resolve this issue, please let me know. Thank you for your attention to this matter.

@berezhinskiy
Copy link
Author

update: I discovered that this issue is only reproduced for port 500/udp

@mzpqnxow
Copy link
Contributor

Build from source and run in gdb, and post the stack trace from there

The built-in stack unwinding (the backtrace you included) is better than nothing, but not as good as gdb output

$ git clone ... && cd masscan && make -j
$ sudo gdb bin/masscan
(gdb) r --wait=0 --open-only --interactive --config ...
...
crash
(gdb) 

Then paste the output from:

(gdb) bt
(gdb) i r

If you do that, I'll take a look

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants