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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade golang-go.crypto | Jul 2, 2019 | May 9, 2019 |
| Redhat Openshift | — | Upgrade atomic-openshift-service-idlerUpgrade openshiftUpgrade openshift-enterprise-autohealUpgrade atomic-openshift-dockerregistryUpgrade golang-github-prometheus-alertmanagerUpgrade golang-github-prometheus-node_exporterUpgrade atomic-openshift-web-consoleUpgrade golang-github-openshift-oauth-proxyUpgrade golang-github-prometheus-prometheusUpgrade atomic-openshiftUpgrade openshift-enterprise-cluster-capacityUpgrade atomic-enterprise-service-catalogUpgrade atomic-openshift-metrics-serverUpgrade atomic-openshift-cluster-autoscalerUpgrade atomic-openshift-node-problem-detectorUpgrade atomic-openshift-descheduler | Dec 29, 2020 | Mar 20, 2019 |
| Ubuntu | — | No solution exists | Jun 26, 2025 | May 9, 2019 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub