CVE Vulnerabilities

CVE-2019-11719

Out-of-bounds Read

Published: Jul 23, 2019 | Modified: Nov 25, 2025
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

When importing a curve25519 private key in PKCS#8format with leading 0x00 bytes, it is possible to trigger an out-of-bounds read in the Network Security Services (NSS) library. This could lead to information disclosure. This vulnerability affects Firefox ESR < 60.8, Firefox < 68, and Thunderbird < 60.8.

Weakness

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

Affected Software

NameVendorStart VersionEnd Version
FirefoxMozilla*60.8.0 (excluding)
FirefoxMozilla*68.0 (excluding)
ThunderbirdMozilla*60.8.0 (excluding)
Red Hat Enterprise Linux 7RedHatnspr-0:4.25.0-2.el7_9*
Red Hat Enterprise Linux 7RedHatnss-0:3.53.1-3.el7_9*
Red Hat Enterprise Linux 7RedHatnss-softokn-0:3.53.1-6.el7_9*
Red Hat Enterprise Linux 7RedHatnss-util-0:3.53.1-1.el7_9*
Red Hat Enterprise Linux 8RedHatnspr-0:4.21.0-2.el8_0*
Red Hat Enterprise Linux 8RedHatnss-0:3.44.0-7.el8_0*
Red Hat OpenShift DoRedHatopenshiftdo/odo-init-image-rhel7:1.1.3-2*
FirefoxUbuntubionic*
FirefoxUbuntucosmic*
FirefoxUbuntudevel*
FirefoxUbuntudisco*
FirefoxUbuntueoan*
FirefoxUbuntufocal*
FirefoxUbuntugroovy*
FirefoxUbuntuhirsute*
FirefoxUbuntuimpish*
FirefoxUbuntujammy*
FirefoxUbuntukinetic*
FirefoxUbuntulunar*
FirefoxUbuntumantic*
FirefoxUbuntunoble*
FirefoxUbuntutrusty*
FirefoxUbuntuupstream*
FirefoxUbuntuxenial*
Mozjs38Ubuntubionic*
Mozjs38Ubuntuesm-apps/bionic*
Mozjs38Ubuntuupstream*
Mozjs52Ubuntubionic*
Mozjs52Ubuntucosmic*
Mozjs52Ubuntudisco*
Mozjs52Ubuntueoan*
Mozjs52Ubuntuesm-apps/focal*
Mozjs52Ubuntuesm-infra/bionic*
Mozjs52Ubuntufocal*
Mozjs52Ubuntugroovy*
Mozjs52Ubuntuupstream*
Mozjs60Ubuntucosmic*
Mozjs60Ubuntudisco*
Mozjs60Ubuntueoan*
Mozjs60Ubuntuupstream*
NssUbuntubionic*
NssUbuntucosmic*
NssUbuntudevel*
NssUbuntudisco*
NssUbuntueoan*
NssUbuntuesm-infra-legacy/trusty*
NssUbuntuesm-infra/bionic*
NssUbuntuesm-infra/focal*
NssUbuntuesm-infra/xenial*
NssUbuntufocal*
NssUbuntugroovy*
NssUbuntuhirsute*
NssUbuntuimpish*
NssUbuntujammy*
NssUbuntukinetic*
NssUbuntulunar*
NssUbuntumantic*
NssUbuntunoble*
NssUbuntutrusty*
NssUbuntutrusty/esm*
NssUbuntuupstream*
NssUbuntuxenial*
ThunderbirdUbuntubionic*
ThunderbirdUbuntucosmic*
ThunderbirdUbuntudevel*
ThunderbirdUbuntudisco*
ThunderbirdUbuntueoan*
ThunderbirdUbuntufocal*
ThunderbirdUbuntugroovy*
ThunderbirdUbuntuhirsute*
ThunderbirdUbuntuimpish*
ThunderbirdUbuntujammy*
ThunderbirdUbuntukinetic*
ThunderbirdUbuntulunar*
ThunderbirdUbuntumantic*
ThunderbirdUbuntunoble*
ThunderbirdUbuntuupstream*
ThunderbirdUbuntuxenial*

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