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.

The remote Debian 10 host has a package installed that is affected by multiple vulnerabilities as referenced in the dla-3455 advisory.

  - 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. (CVE-2019-11840)

  - A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go     cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880     chapter 7, a cleartext signed message can contain one or more optional Hash Armor Headers. The Hash     Armor Header specifies the message digest algorithm(s) used for the signature. However, the Go clearsign     package ignores the value of this header, which allows an attacker to spoof it. Consequently, an attacker     can lead a victim to believe the signature was generated using a different message digest algorithm than     what was actually used. Moreover, since the library skips Armor Header parsing in general, an attacker can     not only embed arbitrary Armor Headers, but also prepend arbitrary text to cleartext messages without     invalidating the signatures. (CVE-2019-11841)

  - golang.org/x/crypto before v0.0.0-20200220183623-bac4c82f6975 for Go allows a panic during signature     verification in the golang.org/x/crypto/ssh package. A client can attack an SSH server that accepts public     keys. Also, a server can attack any SSH client. (CVE-2020-9283)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2021:0079 advisory.

  - golang.org/x/crypto: Keystream loop in amd64 assembly when overflowing 32-bit counter (CVE-2019-11840)

  - python-urllib3: CRLF injection via HTTP request method (CVE-2020-26137)

  - kubernetes: MITM using LoadBalancer or ExternalIPs (CVE-2020-8554)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

golang-go.crypto was recently updated with a fix for CVE-2019-11840.
This in turn requires all packages that use the affected code to be recompiled in order to pick up the security fix.

CVE-2019-11840

An issue was discovered in supplementary Go cryptography libraries, aka golang-googlecode-go-crypto. 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.

For Debian 9 stretch, this problem has been fixed in version 2.21-2+deb9u1.

We recommend that you upgrade your snapd packages.

For the detailed security status of snapd please refer to its security tracker page at: https://security-tracker.debian.org/tracker/snapd

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

golang-go.crypto was recently updated with a fix for CVE-2019-11840.
This in turn requires all packages that use the affected code to be recompiled in order to pick up the security fix.

CVE-2019-11840

An issue was discovered in supplementary Go cryptography libraries, aka golang-googlecode-go-crypto. 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.

For Debian 9 stretch, this problem has been fixed in version 1.35-1+deb8u1.

We recommend that you upgrade your rclone packages.

For the detailed security status of rclone please refer to its security tracker page at:
https://security-tracker.debian.org/tracker/rclone

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

golang-go.crypto was recently updated with a fix for CVE-2019-11840.
This in turn requires all packages that use the affected code to be recompiled in order to pick up the security fix.

CVE-2019-11840

An issue was discovered in supplementary Go cryptography libraries, aka golang-googlecode-go-crypto. 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.

For Debian 9 stretch, this problem has been fixed in version3 0.0.7-1+deb8u1.

We recommend that you upgrade your obfs4proxy packages.

For the detailed security status of obfs4proxy please refer to its security tracker page at:
https://security-tracker.debian.org/tracker/obfs4proxy

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

CVE-2019-11840

An issue was discovered in supplementary Go cryptography libraries, aka golang-googlecode-go-crypto. 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.

CVE-2019-11841

A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries. The 'Hash' Armor Header specifies the message digest algorithm(s) used for the signature. Since the library skips Armor Header parsing in general, an attacker can not only embed arbitrary Armor Headers, but also prepend arbitrary text to cleartext messages without invalidating the signatures.

CVE-2020-9283

golang.org/x/crypto allows a panic during signature verification in the golang.org/x/crypto/ssh package. A client can attack an SSH server that accepts public keys. Also, a server can attack any SSH client.

For Debian 9 stretch, these problems have been fixed in version 1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1+deb8u1.

We recommend that you upgrade your golang-go.crypto packages.

For the detailed security status of golang-go.crypto please refer to its security tracker page at:
https://security-tracker.debian.org/tracker/golang-go.crypto

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

A flaw was found in the amd64 implementation of salsa20. 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.

For Debian 8 'Jessie', this problem has been fixed in version 0.0~hg190-1+deb8u1.

obfs4proxy has been rebuilt as version 0.0.3-2+deb8u1.

We recommend that you upgrade your golang-golang-x-crypto-dev and obfs4proxy packages, and rebuild any software using golang-golang-x-crypto-dev.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
177400	Debian DLA-3455-1 : golang-go.crypto - LTS security update	Nessus	Debian Local Security Checks	medium
145229	RHEL 7 : OpenShift Container Platform 3.11.374 bug fix and (RHSA-2021:0079)	Nessus	Red Hat Local Security Checks	medium
145165	Debian DLA-2527-1 : snapd security update	Nessus	Debian Local Security Checks	medium
143099	Debian DLA-2454-1 : rclone security update	Nessus	Debian Local Security Checks	medium
142667	Debian DLA-2442-1 : obfs4proxy security update	Nessus	Debian Local Security Checks	medium
141271	Debian DLA-2402-1 : golang-go.crypto security update	Nessus	Debian Local Security Checks	medium
126349	Debian DLA-1840-1 : golang-go.crypto security update	Nessus	Debian Local Security Checks	medium

Detections

Analytics

CVE-2019-11840

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium