CVE Vulnerabilities


Exposure of Sensitive Information to an Unauthorized Actor

Published: Mar 11, 2011 | Modified: Jun 03, 2020
CVSS 3.x
CVSS 2.x

Google Chrome before 10.0.648.127 allows remote attackers to bypass the Same Origin Policy via unspecified vectors, related to an error message leak.


The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

Name Vendor Start Version End Version
Chrome Google * *
Chromium-browser Ubuntu artful *
Chromium-browser Ubuntu bionic *
Chromium-browser Ubuntu cosmic *
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 upstream *
Chromium-browser Ubuntu utopic *
Chromium-browser Ubuntu vivid *
Chromium-browser Ubuntu wily *
Chromium-browser Ubuntu xenial *
Chromium-browser Ubuntu yakkety *
Chromium-browser Ubuntu zesty *
Firefox Ubuntu artful *
Firefox Ubuntu bionic *
Firefox Ubuntu cosmic *
Firefox Ubuntu devel *
Firefox Ubuntu esm-infra/bionic *
Firefox Ubuntu esm-infra/xenial *
Firefox Ubuntu hardy *
Firefox Ubuntu lucid *
Firefox Ubuntu natty *
Firefox Ubuntu oneiric *
Firefox Ubuntu precise *
Firefox Ubuntu quantal *
Firefox Ubuntu raring *
Firefox Ubuntu saucy *
Firefox Ubuntu trusty *
Firefox Ubuntu upstream *
Firefox Ubuntu utopic *
Firefox Ubuntu vivid *
Firefox Ubuntu wily *
Firefox Ubuntu xenial *
Firefox Ubuntu yakkety *
Firefox Ubuntu zesty *
Libv8 Ubuntu lucid *
Libv8 Ubuntu maverick *
Libv8 Ubuntu natty *
Libv8 Ubuntu oneiric *
Libv8 Ubuntu precise *
Libv8 Ubuntu quantal *
Libv8 Ubuntu raring *
Libv8 Ubuntu saucy *
Libv8 Ubuntu upstream *
Libv8-3.14 Ubuntu artful *
Libv8-3.14 Ubuntu bionic *
Libv8-3.14 Ubuntu cosmic *
Libv8-3.14 Ubuntu devel *
Libv8-3.14 Ubuntu esm-apps/bionic *
Libv8-3.14 Ubuntu esm-apps/xenial *
Libv8-3.14 Ubuntu saucy *
Libv8-3.14 Ubuntu trusty *
Libv8-3.14 Ubuntu upstream *
Libv8-3.14 Ubuntu utopic *
Libv8-3.14 Ubuntu vivid *
Libv8-3.14 Ubuntu wily *
Libv8-3.14 Ubuntu xenial *
Libv8-3.14 Ubuntu yakkety *
Libv8-3.14 Ubuntu zesty *
Thunderbird Ubuntu hardy *
Thunderbird Ubuntu lucid *
Thunderbird Ubuntu natty *
Thunderbird Ubuntu oneiric *
Thunderbird Ubuntu precise *
Thunderbird Ubuntu upstream *

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.