-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
goproxy v1.1 was discovered to contain an issue which can lead to Denial of Service (DoS) via unspecified vectors #502
Comments
g0ku704
changed the title
panic: runtime error: invalid memory address or nil pointer dereference
goproxy v1.1 was discovered to contain an issue which can lead to Denial of Service (DoS) via unspecified vectors
Jul 18, 2023
jay7x
added a commit
to jay7x/etc-hosts-proxy
that referenced
this issue
Aug 1, 2023
Is this issue resolved ? |
Yes, I've added a nil check that was causing the crash and merged with the main branch now. But the release package is not updated yet. (#507) |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A HTTP request to HTTPS page replaced path the "/" with asterix "*" crashes the elazar/goproxy server in MITM mode.
Vulnerability can be triggered by running this command against elazarl/goproxy in MITM Mode.
Similar to this
https://github.com/elazarl/goproxy/blob/master/https.go#L249
The text was updated successfully, but these errors were encountered: