-
Notifications
You must be signed in to change notification settings - Fork 30
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
fuzzing SOCKS5 ? #79
Comments
I wouldn't say it's impossible to be fuzzed. We don't have any explicit targets for it, but |
The oss-fuzz coverage says socks.c has 0% coverage. But I don't know how to figure out why or what we should/can do to fix this. Ideas welcome! |
I can check it out when I get back off holiday. I thought we'd get it for
free because of the socks5:// protocol, but maybe there's other reasons why
it won't work.
…On Fri, 22 Dec 2023, 09:34 Daniel Stenberg, ***@***.***> wrote:
The oss-fuzz coverage says socks.c has 0% coverage. But I don't know how
to figure out why or what we should/can do to fix this. Ideas welcome!
—
Reply to this email directly, view it on GitHub
<#79 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPA36NYDTKI7BQNKIEXYTLYKVHZJAVCNFSM6AAAAAA55Q3CZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRXGQ2TMOJWGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hello :) Thanks a lot for the great blog post about the recent CVE !
https://daniel.haxx.se/blog/2023/10/11/how-i-made-a-heap-overflow-in-curl/
Just made me wonder if the SOCKS implementation was fuzzed ?
The text was updated successfully, but these errors were encountered: