dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-0169

MEDIUM · 5.0 CVSS v2.0 Published 2010-03-25
Fix available
A fix is available. Upgrade to after 3.0.1 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The CSSLoaderImpl::DoSheetComplete function in layout/style/nsCSSLoader.cpp in Mozilla Firefox 3.0.x before 3.0.18, 3.5.x before 3.5.8, and 3.6.x before 3.6.2; Thunderbird before 3.0.2; and SeaMonkey before 2.0.3 changes the case of certain strings in a stylesheet before adding this stylesheet to the XUL cache, which might allow remote attackers to modify the browser's font and other CSS attributes, and potentially disrupt rendering of a web page, by forcing the browser to perform this erroneous stylesheet caching.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The CSSLoaderImpl::DoSheetComplete function in layout/style/nsCSSLoader.cpp in Mozilla Firefox, Thunderbird, and SeaMonkey changes the case of certain strings in a stylesheet before adding it to the XUL cache. This causes erroneous stylesheet caching that can allow remote attackers to modify the browser's font and other CSS attributes, potentially disrupting web page rendering.

MitigationUpgrade to the fixed versions: Firefox 3.0.18, 3.5.8, or 3.6.2; Thunderbird 3.0.2; or SeaMonkey 2.0.3 or later.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FirefoxWeb browser
Affected:= 3.0= 3.0.1= 3.0.10= 3.0.11= 3.0.12= 3.0.13= 3.0.14= 3.0.15= 3.0.16= 3.0.17= 3.5= 3.5.1
SeamonkeyApplication
Affected:<= 2.0.2= 1.1= 1.1.1= 1.1.2= 1.1.3= 1.1.4= 1.1.5= 1.1.6= 1.1.7= 1.1.8= 1.1.9= 1.1.10
ThunderbirdApplication
Affected:<= 3.0.1= 1.5= 1.5.0.1= 1.5.0.2= 1.5.0.3= 1.5.0.4= 1.5.0.5= 1.5.0.6= 1.5.0.7= 1.5.0.8= 1.5.0.9= 1.5.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Mozilla product
    Check which application is installed: Firefox, Thunderbird, or SeaMonkey. On Windows, look in Program Files; on macOS, check /Applications; on Linux, check /usr/lib or via package manager.
    Affected if Any of these three products is installed
  2. Determine Firefox version
    For Firefox, run 'firefox -version' from command line, or open Help > About Firefox, or check the version in the application.ini or platform.ini file in the Firefox installation directory.
    Affected if Version is 3.0.x (3.0 through 3.0.17), 3.5.x (3.5 or 3.5.1), or falls within any other affected range listed in the CVE
  3. Determine Thunderbird version
    For Thunderbird, run 'thunderbird -version' from command line, or open Help > About Thunderbird, or check the version in the application.ini file in the Thunderbird installation directory.
    Affected if Version is 1.5.x (1.5 through 1.5.0.10), 3.0.x (3.0 or 3.0.1), or falls within any other affected range listed in the CVE
  4. Determine SeaMonkey version
    For SeaMonkey, run 'seamonkey -version' from command line, or open Help > About SeaMonkey, or check the version in the application.ini file in the SeaMonkey installation directory.
    Affected if Version is 1.1.x (1.1 through 1.1.10), 2.0.x (2.0 through 2.0.2), or falls within any other affected range listed in the CVE

If the installed product is Firefox, Thunderbird, or SeaMonkey and the version matches any of the affected versions listed in the CVE (Firefox 3.0-3.0.17 or 3.5-3.5.1; Thunderbird 1.5-1.5.0.10 or 3.0-3.0.1; SeaMonkey 1.1-1.1.10 or 2.0-2.0.2), the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 3.0.1
Interim mitigation

Upgrade to the fixed versions: Firefox 3.0.18, 3.5.8, or 3.6.2; Thunderbird 3.0.2; or SeaMonkey 2.0.3 or later.

Fix this in Firefox Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0169 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0169 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data