CVE Vulnerabilities

CVE-2013-0767

Out-of-bounds Read

Published: Jan 13, 2013 | Modified: Oct 21, 2024
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
10 HIGH
AV:N/AC:L/Au:N/C:C/I:C/A:C
RedHat/V2
6.8 CRITICAL
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V3
Ubuntu
MEDIUM

The nsSVGPathElement::GetPathLengthScale function in Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.1, Thunderbird before 17.0.2, Thunderbird ESR 10.x before 10.0.12 and 17.x before 17.0.1, and SeaMonkey before 2.15 allows remote attackers to execute arbitrary code or cause a denial of service (out-of-bounds read) via unspecified vectors.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Firefox Mozilla * 18.0 (excluding)
Firefox Mozilla 10.0 (including) 10.0.12 (excluding)
Firefox Mozilla 17.0 (including) 17.0.2 (excluding)
Seamonkey Mozilla * 2.15 (excluding)
Thunderbird Mozilla * 17.0.2 (excluding)
Thunderbird_esr Mozilla 10.0 (including) 10.0.12 (excluding)
Thunderbird_esr Mozilla 17.0 (including) 17.0.2 (excluding)
Red Hat Enterprise Linux 5 RedHat thunderbird-0:10.0.12-3.el5_9 *
Red Hat Enterprise Linux 5 RedHat firefox-0:10.0.12-1.el5_9 *
Red Hat Enterprise Linux 5 RedHat xulrunner-0:10.0.12-1.el5_9 *
Red Hat Enterprise Linux 6 RedHat firefox-0:10.0.12-1.el6_3 *
Red Hat Enterprise Linux 6 RedHat xulrunner-0:10.0.12-1.el6_3 *
Red Hat Enterprise Linux 6 RedHat thunderbird-0:10.0.12-3.el6_3 *
Firefox Ubuntu devel *
Firefox Ubuntu hardy *
Firefox Ubuntu lucid *
Firefox Ubuntu oneiric *
Firefox Ubuntu precise *
Firefox Ubuntu quantal *
Firefox Ubuntu raring *
Firefox Ubuntu saucy *
Firefox Ubuntu upstream *
Seamonkey Ubuntu hardy *
Seamonkey Ubuntu lucid *
Seamonkey Ubuntu oneiric *
Seamonkey Ubuntu upstream *
Thunderbird Ubuntu devel *
Thunderbird Ubuntu hardy *
Thunderbird Ubuntu lucid *
Thunderbird Ubuntu oneiric *
Thunderbird Ubuntu precise *
Thunderbird Ubuntu quantal *
Thunderbird Ubuntu raring *
Thunderbird Ubuntu saucy *
Thunderbird Ubuntu upstream *

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