An issue was discovered in supplementary Go cryptography libraries, aka golang-googlecode-go-crypto, before 2019-03-20. A flaw was found in the amd64 implementation of golang.org/x/crypto/salsa20 and golang.org/x/crypto/salsa20/salsa. 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.
bugzilla.redhat.com/show_bug.cgi?id=1691529
github.com/advisories/GHSA-r5c5-pr8j-pfp7
github.com/golang/go/issues/30965
go.dev/cl/168406
go.dev/issue/30965
go.googlesource.com/crypto/+/b7391e95e576cacdcdd422573063bc057239113d
groups.google.com/forum/#!msg/golang-announce/tjyNcJxb2vQ/n0NRBziSCAAJ
groups.google.com/g/golang-announce/c/tjyNcJxb2vQ/m/n0NRBziSCAAJ
lists.debian.org/debian-lts-announce/2019/06/msg00029.html
lists.debian.org/debian-lts-announce/2020/10/msg00014.html
lists.debian.org/debian-lts-announce/2020/11/msg00016.html
lists.debian.org/debian-lts-announce/2020/11/msg00030.html
lists.debian.org/debian-lts-announce/2021/01/msg00015.html
nvd.nist.gov/vuln/detail/CVE-2019-11840
pkg.go.dev/vuln/GO-2022-0209