CVE Vulnerabilities

CVE-2020-12403

Out-of-bounds Read

Published: May 27, 2021 | Modified: Mar 24, 2023
CVSS 3.x
9.1
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
CVSS 2.x
6.4 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:P
RedHat/V2
RedHat/V3
7.4 MODERATE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H
Ubuntu
MEDIUM

A flaw was found in the way CHACHA20-POLY1305 was implemented in NSS in versions before 3.55. When using multi-part Chacha20, it could cause out-of-bounds reads. This issue was fixed by explicitly disabling multi-part ChaCha20 (which was not functioning correctly) and strictly enforcing tag length. The highest threat from this vulnerability is to confidentiality and system availability.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Nss Mozilla * 3.55 (excluding)
Nss Ubuntu bionic *
Nss Ubuntu devel *
Nss Ubuntu focal *
Nss Ubuntu trusty *
Nss Ubuntu trusty/esm *
Nss Ubuntu upstream *
Nss Ubuntu xenial *
Red Hat Enterprise Linux 7 RedHat nspr-0:4.25.0-2.el7_9 *
Red Hat Enterprise Linux 7 RedHat nss-0:3.53.1-3.el7_9 *
Red Hat Enterprise Linux 7 RedHat nss-softokn-0:3.53.1-6.el7_9 *
Red Hat Enterprise Linux 7 RedHat nss-util-0:3.53.1-1.el7_9 *
Red Hat Enterprise Linux 7.4 Advanced Update Support RedHat nss-softokn-0:3.28.3-10.el7_4 *
Red Hat Enterprise Linux 7.4 Telco Extended Update Support RedHat nss-softokn-0:3.28.3-10.el7_4 *
Red Hat Enterprise Linux 7.4 Update Services for SAP Solutions RedHat nss-softokn-0:3.28.3-10.el7_4 *
Red Hat Enterprise Linux 7.6 Extended Update Support RedHat nss-0:3.36.0-9.el7_6 *
Red Hat Enterprise Linux 7.6 Extended Update Support RedHat nss-softokn-0:3.36.0-7.el7_6 *
Red Hat Enterprise Linux 7.7 Extended Update Support RedHat nss-softokn-0:3.44.0-9.el7_7 *
Red Hat Enterprise Linux 8 RedHat nss-0:3.53.1-17.el8_3 *
Red Hat OpenShift Do RedHat openshiftdo/odo-init-image-rhel7:1.1.3-2 *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References