CVE Vulnerabilities


Out-of-bounds Read

Published: Feb 16, 2012 | Modified: Apr 16, 2020
CVSS 3.x
CVSS 2.x

Google Chrome before 17.0.963.56 does not properly parse H.264 data, which allows remote attackers to cause a denial of service (out-of-bounds read) via unspecified vectors.


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

Affected Software

Name Vendor Start Version End Version
Chrome Google * *
Chromium-browser Ubuntu devel *
Chromium-browser Ubuntu lucid *
Chromium-browser Ubuntu maverick *
Chromium-browser Ubuntu natty *
Chromium-browser Ubuntu oneiric *
Chromium-browser Ubuntu precise *
Chromium-browser Ubuntu quantal *
Chromium-browser Ubuntu raring *
Chromium-browser Ubuntu saucy *
Chromium-browser Ubuntu trusty *
Chromium-browser Ubuntu utopic *
Chromium-browser Ubuntu vivid *
Chromium-browser Ubuntu wily *
Chromium-browser Ubuntu xenial *
Chromium-browser Ubuntu yakkety *
Qtwebkit-source Ubuntu devel *
Qtwebkit-source Ubuntu esm-apps/xenial *
Qtwebkit-source Ubuntu maverick *
Qtwebkit-source Ubuntu natty *
Qtwebkit-source Ubuntu oneiric *
Qtwebkit-source Ubuntu precise *
Qtwebkit-source Ubuntu quantal *
Qtwebkit-source Ubuntu raring *
Qtwebkit-source Ubuntu saucy *
Qtwebkit-source Ubuntu trusty *
Qtwebkit-source Ubuntu utopic *
Qtwebkit-source Ubuntu vivid *
Qtwebkit-source Ubuntu wily *
Qtwebkit-source Ubuntu xenial *
Qtwebkit-source Ubuntu yakkety *
Webkit Ubuntu hardy *
Webkit Ubuntu lucid *
Webkit Ubuntu maverick *
Webkit Ubuntu natty *
Webkit Ubuntu oneiric *
Webkit Ubuntu precise *
Webkit Ubuntu quantal *
Webkit Ubuntu raring *
Webkit Ubuntu saucy *
Webkitgtk Ubuntu utopic *
Webkitgtk Ubuntu vivid *

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.