Use of Insufficiently Random Values Affecting golang-go.crypto package, versions <1:0.0~git20200221.2aa609c-1


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.69% (81st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of Insufficiently Random Values vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIANUNSTABLE-GOLANGGOCRYPTO-347880
  • published9 May 2019
  • disclosed9 May 2019

Introduced: 9 May 2019

CVE-2019-11840  (opens in a new tab)
CWE-330  (opens in a new tab)

How to fix?

Upgrade Debian:unstable golang-go.crypto to version 1:0.0~git20200221.2aa609c-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream golang-go.crypto package and not the golang-go.crypto package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

CVSS Scores

version 3.1