CVE Vulnerabilities


Exposure of Sensitive Information to an Unauthorized Actor

Published: Jul 07, 2008 | Modified: Oct 11, 2018
CVSS 3.x
CVSS 2.x

Mozilla Firefox before and SeaMonkey before 1.1.10 do not properly handle an invalid .properties file for an add-on, which allows remote attackers to read uninitialized memory, as demonstrated by use of ISO 8859 encoding instead of UTF-8 encoding in a French .properties file.


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 2.0 2.0
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla
Firefox Mozilla *
Seamonkey Mozilla 1.1 1.1
Seamonkey Mozilla 1.1.2 1.1.2
Seamonkey Mozilla 1.1.3 1.1.3
Seamonkey Mozilla 1.1.4 1.1.4
Seamonkey Mozilla 1.1.5 1.1.5
Seamonkey Mozilla 1.1.6 1.1.6
Seamonkey Mozilla 1.1.7 1.1.7
Seamonkey Mozilla 1.1.8 1.1.8
Seamonkey Mozilla * 1.1.9
Red Hat Enterprise Linux 2.1 RedHat seamonkey-0:1.0.9-0.17.el2 *
Red Hat Enterprise Linux 3 RedHat seamonkey-0:1.0.9-0.20.el3 *
Red Hat Enterprise Linux 4 RedHat seamonkey-0:1.0.9-16.3.el4_6 *
Red Hat Enterprise Linux 4 RedHat firefox-0: *
Red Hat Enterprise Linux 4 RedHat thunderbird-0: *
Red Hat Enterprise Linux 5 RedHat devhelp-0:0.12-17.el5 *
Red Hat Enterprise Linux 5 RedHat firefox-0:3.0-2.el5 *
Red Hat Enterprise Linux 5 RedHat xulrunner-0:1.9-1.el5 *
Red Hat Enterprise Linux 5 RedHat yelp-0:2.16.0-19.el5 *
Red Hat Enterprise Linux 5 RedHat thunderbird-0: *
Firefox Ubuntu dapper *
Firefox Ubuntu feisty *
Firefox Ubuntu gutsy *
Firefox Ubuntu hardy *
Firefox Ubuntu upstream *
Firefox-3.0 Ubuntu gutsy *
Iceape Ubuntu gutsy *
Icedove Ubuntu upstream *
Iceweasel Ubuntu upstream *
Mozilla-thunderbird Ubuntu dapper *
Mozilla-thunderbird Ubuntu feisty *
Seamonkey Ubuntu devel *
Seamonkey Ubuntu hardy *
Seamonkey Ubuntu intrepid *
Seamonkey Ubuntu jaunty *
Seamonkey Ubuntu karmic *
Seamonkey Ubuntu lucid *
Seamonkey Ubuntu maverick *
Seamonkey Ubuntu natty *
Seamonkey Ubuntu upstream *
Thunderbird Ubuntu devel *
Thunderbird Ubuntu gutsy *
Thunderbird Ubuntu hardy *
Thunderbird Ubuntu intrepid *
Thunderbird Ubuntu jaunty *
Thunderbird Ubuntu karmic *
Thunderbird Ubuntu lucid *
Thunderbird Ubuntu maverick *
Thunderbird Ubuntu natty *
Thunderbird Ubuntu upstream *
Xulrunner Ubuntu feisty *
Xulrunner Ubuntu gutsy *
Xulrunner Ubuntu hardy *
Xulrunner Ubuntu intrepid *
Xulrunner Ubuntu jaunty *
Xulrunner Ubuntu karmic *

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.