Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

n/a · Vulnerability

cve-program · severity unknowneuvd · severity unknownCVSS 3.1 · [email protected] · Primary 5.9 MEDIUMCVSS 2.0 · [email protected] · Primary 4.3 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by golang.org/x/crypto 0.0.0-20190320223903-b7391e95e576osv · severity unknownFixed by golang.org/x/crypto 0.0.0-20190320223903-b7391e95e576KEV status unknown

cve-program · CVE-2019-11840

Published

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.

Read the publisher's advisory

euvd · EUVD-2022-5096

Published

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.

Read the publisher's advisory

nvd · CVE-2019-11840

Published

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.

Read the publisher's advisory

osv · GHSA-r5c5-pr8j-pfp7

Published

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. ### Specific Go Packages Affected golang.org/x/crypto/salsa20/salsa

Read the publisher's advisory

osv · GO-2022-0209

Published

XORKeyStream generates incorrect and insecure output for very large inputs. 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. The issue might affect uses of golang.org/x/crypto/nacl with extremely large messages. Architectures other than amd64 and uses that generate less than 256 GiB of keystream for a single salsa20.XORKeyStream invocation are unaffected.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2019-11840

Published

n/a

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "n/a",
                    "product": "n/a",
                    "versions": [
                        {
                            "version": "n/a",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2022-5096

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: May 9, 2019, 12:00:00 AM

dateUpdated: Aug 4, 2024, 11:03:32 PM

4 related source bulletins · separate from aliases

WID-SEC-W-2022-0496: Red Hat OpenShift: Mehrere Schwachstellen

CVE-2019-11840 · CVE-2020-26137

RHBA-2020:0062: Red Hat Bug Fix Advisory: OpenShift Container Platform 4.3 image release advisory

CVE-2019-11840 · CVE-2019-16276

RHBA-2020:0063: Red Hat Bug Fix Advisory: OpenShift Container Platform 4.3 RPM release advisory

CVE-2019-10401 · CVE-2019-10402 · CVE-2019-10403 · CVE-2019-10404 · CVE-2019-10405 · CVE-2019-10406 · CVE-2019-11840

RHSA-2021:0079: Red Hat Security Advisory: OpenShift Container Platform 3.11.374 bug fix and security update

CVE-2019-11840 · CVE-2020-8554 · CVE-2020-26137

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2019-11840

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-330

Original publisher date fields

published: 2019-05-09T16:29:00.607

lastModified: 2026-06-17T02:13:43.400

4 source CPE criteria · context only
  • cpe:2.3:a:golang:crypto:-:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-r5c5-pr8j-pfp7

Published

golang.org/x/crypto

Go

SEMVER · introduced 0 → fixed 0.0.0-20190320223903-b7391e95e576

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2022-0209

Published

golang.org/x/crypto

Go

SEMVER · introduced 0 → fixed 0.0.0-20190320223903-b7391e95e576

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current