CVE Vulnerabilities

CVE-2019-12750

Out-of-bounds Read

Published: Jul 31, 2019 | Modified: Aug 24, 2020
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
4.6 MEDIUM
AV:L/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

Symantec Endpoint Protection, prior to 14.2 RU1 & 12.1 RU6 MP10 and Symantec Endpoint Protection Small Business Edition, prior to 12.1 RU6 MP10c (12.1.7491.7002), may be susceptible to a privilege escalation vulnerability, which is a type of issue whereby an attacker may attempt to compromise the software application to gain elevated access to resources that are normally protected from an application or user.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 11.0 11.0
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 12.1 12.1
Endpoint_protection Symantec 14.0.0 14.0.0
Endpoint_protection Symantec 14.0.0 14.0.0
Endpoint_protection Symantec 14.0.0 14.0.0
Endpoint_protection Symantec 14.0.1 14.0.1
Endpoint_protection Symantec 14.0.1 14.0.1
Endpoint_protection Symantec 14.0.1 14.0.1
Endpoint_protection Symantec 14.2 14.2
Endpoint_protection Symantec 14.2 14.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