-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
archive/tar: slice bounds out of range #10959
Comments
Neat bug, but I don't have time to pick it up. |
It's also probably been there forever, so I don't think it's critical for go1.5. |
heartbleed was also there forever |
If you can make a case that this is a security hole (beyond just a DoS vector) then we can reprioritise. |
DoS can also be an issue. Note that you can use this bug to (1) cause a panic, (2) cause swapping and affect the whole machine or (3) terminate the program instantly with a fatal error at your discretion. I don't have anything more serious. This does not mean that a bad guy does not have the other part of the puzzle and he just waits for a way to force a server to panic (panic/defer/recover mechanism did have a bunch of bugs that compromise memory safety). |
CL https://golang.org/cl/10402 mentions this issue. |
The following program crashes with a panic:
on commit 8017ace
The text was updated successfully, but these errors were encountered: