The calculated severity for CVEs has been updated to use CVSS v3 by default. CVEs that do not have a CVSS v3 score will fall back CVSS v2 for calculating severity. Severity display preferences can be toggled in the settings dropdown.
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.
Base Score: 4.3
Impact Score: 2.9
Exploitability Score: 8.6
Base Score: 5.9
Impact Score: 3.6
Exploitability Score: 2.2
|145229||RHEL 7 : OpenShift Container Platform 3.11.374 bug fix and (RHSA-2021:0079)||Nessus||Red Hat Local Security Checks|
|145165||Debian DLA-2527-1 : snapd security update||Nessus||Debian Local Security Checks|
|143099||Debian DLA-2454-1 : rclone security update||Nessus||Debian Local Security Checks|
|142667||Debian DLA-2442-1 : obfs4proxy security update||Nessus||Debian Local Security Checks|
|141271||Debian DLA-2402-1 : golang-go.crypto security update||Nessus||Debian Local Security Checks|
|126349||Debian DLA-1840-1 : golang-go.crypto security update||Nessus||Debian Local Security Checks|