An issue was discovered in the supplementary Go cryptography library, golang.org/x/crypto, before v0.0.0-20190320223903-b7391e95e576. A flaw was found in the amd64 implementation of the golang.org/x/crypto/salsa20 and golang.org/x/crypto/salsa20/salsa packages. If more than 256 GiB of keystream is generated, or if the counter otherwise grows greater than 32 bits, the amd64 implementation will first generate incorrect output, and then cycle back to previously generated keystream. Repeated keystream bytes can lead to loss of confidentiality in encryption applications, or to predictability in CSPRNG applications.
References
Link | Resource |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=1691529 | Issue Tracking Vendor Advisory |
https://github.com/golang/go/issues/30965 | Third Party Advisory |
https://go.googlesource.com/crypto/+/b7391e95e576cacdcdd422573063bc057239113d | Mailing List Patch Third Party Advisory |
https://groups.google.com/forum/#%21msg/golang-announce/tjyNcJxb2vQ/n0NRBziSCAAJ | |
https://lists.debian.org/debian-lts-announce/2019/06/msg00029.html | Mailing List Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2020/10/msg00014.html | Mailing List Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2020/11/msg00016.html | Mailing List Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2020/11/msg00030.html | Mailing List Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2021/01/msg00015.html | Mailing List Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2023/06/msg00017.html | |
https://pkg.go.dev/vuln/GO-2022-0209 |
Configurations
History
14 May 2024, 05:37
Type | Values Removed | Values Added |
---|---|---|
Summary | (en) An issue was discovered in the supplementary Go cryptography library, golang.org/x/crypto, before v0.0.0-20190320223903-b7391e95e576. A flaw was found in the amd64 implementation of the golang.org/x/crypto/salsa20 and golang.org/x/crypto/salsa20/salsa packages. If more than 256 GiB of keystream is generated, or if the counter otherwise grows greater than 32 bits, the amd64 implementation will first generate incorrect output, and then cycle back to previously generated keystream. Repeated keystream bytes can lead to loss of confidentiality in encryption applications, or to predictability in CSPRNG applications. | |
References |
|
07 Nov 2023, 03:03
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
17 Jun 2023, 00:15
Type | Values Removed | Values Added |
---|---|---|
References |
|
Information
Published : 2019-05-09 16:29
Updated : 2024-05-14 05:37
NVD link : CVE-2019-11840
Mitre link : CVE-2019-11840
CVE.ORG link : CVE-2019-11840
JSON object : View
Products Affected
debian
- debian_linux
golang
- crypto
CWE
CWE-330
Use of Insufficiently Random Values