CVE Vulnerabilities

CVE-2019-20503

Out-of-bounds Read

Published: Mar 06, 2020 | Modified: Jun 27, 2024
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
6.1 MODERATE
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Ubuntu
MEDIUM

usrsctp before 2019-12-20 has out-of-bounds reads in sctp_load_addresses_from_init.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Usrsctp Usrsctp_project * 0.9.4.0 (excluding)
Chromium-browser Ubuntu bionic *
Chromium-browser Ubuntu trusty *
Chromium-browser Ubuntu upstream *
Chromium-browser Ubuntu xenial *
Firefox Ubuntu bionic *
Firefox Ubuntu devel *
Firefox Ubuntu eoan *
Firefox Ubuntu focal *
Firefox Ubuntu groovy *
Firefox Ubuntu hirsute *
Firefox Ubuntu impish *
Firefox Ubuntu jammy *
Firefox Ubuntu kinetic *
Firefox Ubuntu lunar *
Firefox Ubuntu mantic *
Firefox Ubuntu noble *
Firefox Ubuntu oracular *
Firefox Ubuntu trusty *
Firefox Ubuntu upstream *
Firefox Ubuntu xenial *
Libusrsctp Ubuntu eoan *
Libusrsctp Ubuntu groovy *
Libusrsctp Ubuntu hirsute *
Libusrsctp Ubuntu impish *
Libusrsctp Ubuntu kinetic *
Libusrsctp Ubuntu lunar *
Libusrsctp Ubuntu mantic *
Libusrsctp Ubuntu trusty *
Thunderbird Ubuntu bionic *
Thunderbird Ubuntu devel *
Thunderbird Ubuntu eoan *
Thunderbird Ubuntu focal *
Thunderbird Ubuntu groovy *
Thunderbird Ubuntu hirsute *
Thunderbird Ubuntu impish *
Thunderbird Ubuntu jammy *
Thunderbird Ubuntu kinetic *
Thunderbird Ubuntu lunar *
Thunderbird Ubuntu mantic *
Thunderbird Ubuntu noble *
Thunderbird Ubuntu oracular *
Thunderbird Ubuntu trusty *
Thunderbird Ubuntu upstream *
Thunderbird Ubuntu xenial *
Red Hat Enterprise Linux 6 RedHat firefox-0:68.6.0-1.el6_10 *
Red Hat Enterprise Linux 6 RedHat thunderbird-0:68.6.0-1.el6_10 *
Red Hat Enterprise Linux 6 Supplementary RedHat chromium-browser-0:80.0.3987.149-1.el6_10 *
Red Hat Enterprise Linux 7 RedHat firefox-0:68.6.0-1.el7_7 *
Red Hat Enterprise Linux 7 RedHat thunderbird-0:68.6.0-1.el7_7 *
Red Hat Enterprise Linux 8 RedHat firefox-0:68.6.0-1.el8_1 *
Red Hat Enterprise Linux 8 RedHat thunderbird-0:68.6.0-1.el8_1 *
Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions RedHat firefox-0:68.6.0-1.el8_0 *
Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions RedHat thunderbird-0:68.6.0-1.el8_0 *

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