CVE Vulnerabilities

CVE-2012-1960

Exposure of Sensitive Information to an Unauthorized Actor

Published: Jul 18, 2012 | Modified: Dec 29, 2017
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
3.3 LOW
AV:L/AC:M/Au:N/C:P/I:N/A:P
RedHat/V3
Ubuntu
LOW

The qcms_transform_data_rgb_out_lut_sse2 function in the QCMS implementation in Mozilla Firefox 4.x through 13.0, Thunderbird 5.0 through 13.0, and SeaMonkey before 2.11 might allow remote attackers to obtain sensitive information from process memory via a crafted color profile that triggers an out-of-bounds read operation.

Weakness

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 (including) 4.0 (including)
Firefox Mozilla 4.0-beta1 (including) 4.0-beta1 (including)
Firefox Mozilla 4.0-beta10 (including) 4.0-beta10 (including)
Firefox Mozilla 4.0-beta11 (including) 4.0-beta11 (including)
Firefox Mozilla 4.0-beta12 (including) 4.0-beta12 (including)
Firefox Mozilla 4.0-beta2 (including) 4.0-beta2 (including)
Firefox Mozilla 4.0-beta3 (including) 4.0-beta3 (including)
Firefox Mozilla 4.0-beta4 (including) 4.0-beta4 (including)
Firefox Mozilla 4.0-beta5 (including) 4.0-beta5 (including)
Firefox Mozilla 4.0-beta6 (including) 4.0-beta6 (including)
Firefox Mozilla 4.0-beta7 (including) 4.0-beta7 (including)
Firefox Mozilla 4.0-beta8 (including) 4.0-beta8 (including)
Firefox Mozilla 4.0-beta9 (including) 4.0-beta9 (including)
Firefox Mozilla 4.0.1 (including) 4.0.1 (including)
Firefox Mozilla 5.0 (including) 5.0 (including)
Firefox Mozilla 5.0.1 (including) 5.0.1 (including)
Firefox Mozilla 6.0 (including) 6.0 (including)
Firefox Mozilla 6.0.1 (including) 6.0.1 (including)
Firefox Mozilla 6.0.2 (including) 6.0.2 (including)
Firefox Mozilla 7.0 (including) 7.0 (including)
Firefox Mozilla 7.0.1 (including) 7.0.1 (including)
Firefox Mozilla 8.0 (including) 8.0 (including)
Firefox Mozilla 8.0.1 (including) 8.0.1 (including)
Firefox Mozilla 9.0 (including) 9.0 (including)
Firefox Mozilla 9.0.1 (including) 9.0.1 (including)
Firefox Mozilla 11.0 (including) 11.0 (including)
Firefox Mozilla 12.0 (including) 12.0 (including)
Firefox Mozilla 12.0-beta6 (including) 12.0-beta6 (including)
Firefox Mozilla 13.0 (including) 13.0 (including)
Firefox Ubuntu hardy *
Firefox Ubuntu lucid *
Firefox Ubuntu natty *
Firefox Ubuntu oneiric *
Firefox Ubuntu precise *
Firefox Ubuntu upstream *
Seamonkey Ubuntu hardy *
Seamonkey Ubuntu lucid *
Seamonkey Ubuntu natty *
Seamonkey Ubuntu oneiric *
Thunderbird Ubuntu hardy *
Thunderbird Ubuntu lucid *
Thunderbird Ubuntu natty *
Thunderbird Ubuntu oneiric *
Thunderbird Ubuntu precise *
Thunderbird Ubuntu upstream *
Xulrunner-1.9.2 Ubuntu hardy *
Xulrunner-1.9.2 Ubuntu lucid *
Xulrunner-1.9.2 Ubuntu natty *
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.

References