-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/crypto/openpgp: ReadMessage(): Panic on invalid input in packet.nextSubpacket() (slice bounds out of range) #11503
Labels
Milestone
Comments
marete
changed the title
x/crypto/openpgp: Panic on invalid input in packet.nextSubpacket() (slice bounds out of range)
x/crypto/openpgp: ReadMessage(): Panic on invalid input in packet.nextSubpacket() (slice bounds out of range)
Jul 1, 2015
CC @agl |
Submitted CL https://go-review.googlesource.com/#/c/12634/ to fix this issue. |
CL https://golang.org/cl/12634 mentions this issue. |
benburkert
pushed a commit
to benburkert/openpgp
that referenced
this issue
Feb 29, 2016
Some invalid input may be parsed so that the length of an opaque subpacket turns out to be 0. In such cases, arrange for a StructuralError to be returned indicating truncation. Found using gofuzz. Fixes golang/go#11503 Change-Id: Ib9ce8c604f35a31f852adfcd56a22dfd143a9443 Reviewed-on: https://go-review.googlesource.com/12634 Reviewed-by: Adam Langley <agl@golang.org>
c-expert-zigbee
pushed a commit
to c-expert-zigbee/crypto_go
that referenced
this issue
Mar 28, 2022
Some invalid input may be parsed so that the length of an opaque subpacket turns out to be 0. In such cases, arrange for a StructuralError to be returned indicating truncation. Found using gofuzz. Fixes golang/go#11503 Change-Id: Ib9ce8c604f35a31f852adfcd56a22dfd143a9443 Reviewed-on: https://go-review.googlesource.com/12634 Reviewed-by: Adam Langley <agl@golang.org>
c-expert-zigbee
pushed a commit
to c-expert-zigbee/crypto_go
that referenced
this issue
Mar 29, 2022
Some invalid input may be parsed so that the length of an opaque subpacket turns out to be 0. In such cases, arrange for a StructuralError to be returned indicating truncation. Found using gofuzz. Fixes golang/go#11503 Change-Id: Ib9ce8c604f35a31f852adfcd56a22dfd143a9443 Reviewed-on: https://go-review.googlesource.com/12634 Reviewed-by: Adam Langley <agl@golang.org>
BiiChris
pushed a commit
to BiiChris/crypto
that referenced
this issue
Sep 15, 2023
Some invalid input may be parsed so that the length of an opaque subpacket turns out to be 0. In such cases, arrange for a StructuralError to be returned indicating truncation. Found using gofuzz. Fixes golang/go#11503 Change-Id: Ib9ce8c604f35a31f852adfcd56a22dfd143a9443 Reviewed-on: https://go-review.googlesource.com/12634 Reviewed-by: Adam Langley <agl@golang.org>
desdeel2d0m
added a commit
to desdeel2d0m/crypto
that referenced
this issue
Jul 1, 2024
Some invalid input may be parsed so that the length of an opaque subpacket turns out to be 0. In such cases, arrange for a StructuralError to be returned indicating truncation. Found using gofuzz. Fixes golang/go#11503 Change-Id: Ib9ce8c604f35a31f852adfcd56a22dfd143a9443 Reviewed-on: https://go-review.googlesource.com/12634 Reviewed-by: Adam Langley <agl@golang.org>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The following program panics:
with the trace:
Found using gofuzz. You may assign this issue to me.
The text was updated successfully, but these errors were encountered: