CVE Vulnerabilities


Exposure of Sensitive Information to an Unauthorized Actor

Published: Aug 18, 2011 | Modified: Sep 19, 2017
CVSS 3.x
CVSS 2.x

Mozilla Firefox 4.x through 5, Thunderbird before 6, SeaMonkey 2.x before 2.3, and possibly other products, when the Direct2D (aka D2D) API is used on Windows, allows remote attackers to bypass the Same Origin Policy, and obtain sensitive image data from a different domain, by inserting this data into a canvas.


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
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0 4.0
Firefox Mozilla 4.0.1 4.0.1
Firefox Mozilla 5.0 5.0
Firefox Ubuntu hardy *
Firefox Ubuntu lucid *
Firefox Ubuntu maverick *
Firefox Ubuntu natty *
Firefox Ubuntu upstream *
Seamonkey Ubuntu devel *
Seamonkey Ubuntu hardy *
Seamonkey Ubuntu lucid *
Seamonkey Ubuntu maverick *
Seamonkey Ubuntu natty *
Thunderbird Ubuntu devel *
Thunderbird Ubuntu hardy *
Thunderbird Ubuntu lucid *
Thunderbird Ubuntu maverick *
Thunderbird Ubuntu natty *
Thunderbird Ubuntu upstream *
Xulrunner-1.9.2 Ubuntu hardy *
Xulrunner-1.9.2 Ubuntu lucid *
Xulrunner-1.9.2 Ubuntu maverick *
Xulrunner-1.9.2 Ubuntu natty *
Xulrunner-1.9.2 Ubuntu upstream *
Xulrunner-2.0 Ubuntu natty *

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.