dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-2752

HIGH · 9.3 CVSS v2.0 Published 2010-07-30
Fix available
A fix is available. Upgrade to after 2.0.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Integer overflow in an array class in Mozilla Firefox 3.5.x before 3.5.11 and 3.6.x before 3.6.7, Thunderbird 3.0.x before 3.0.6 and 3.1.x before 3.1.1, and SeaMonkey before 2.0.6 allows remote attackers to execute arbitrary code by placing many Cascading Style Sheets (CSS) values in an array, related to references to external font resources and an inconsistency between 16-bit and 32-bit integers.

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

Integer overflow vulnerability in the array class handling CSS values in Mozilla Firefox 3.5.x/3.6.x, Thunderbird 3.0.x/3.1.x, and SeaMonkey. The flaw stems from a 16-bit/32-bit integer inconsistency when processing large numbers of CSS values related to external font resources, allowing remote attackers to execute arbitrary code.

MitigationUpgrade to Firefox 3.5.11/3.6.7, Thunderbird 3.0.6/3.1.1, SeaMonkey 2.0.6 or later; or remove these legacy products from the environment if patching is not feasible.

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.5.1= 3.5.2= 3.5.3= 3.5.4= 3.5.5= 3.5.6= 3.5.7= 3.5.9= 3.5.10= 3.6.1= 3.6.2= 3.6.3
ThunderbirdApplication
Affected:= 3.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5= 3.1
SeamonkeyApplication
Affected:<= 2.0.5= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.0.9= 1.1

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 Firefox version
    Run 'firefox --version' in command line, or open Firefox and go to Help > About Firefox
    Affected if Version is 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.5.5, 3.5.6, 3.5.7, 3.5.9, 3.5.10, 3.6.1, 3.6.2, or 3.6.3
  2. Identify installed Thunderbird version
    Run 'thunderbird --version' in command line, or open Thunderbird and go to Help > About Thunderbird
    Affected if Version is 3.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, or 3.1
  3. Identify installed SeaMonkey version
    Run 'seamonkey --version' in command line, or open SeaMonkey and go to Help > About SeaMonkey
    Affected if Version is 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1, or 2.0.5 or earlier

The environment is affected if any of these Mozilla products are present with a version matching one of the specific versions listed in the affected ranges.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.0.5
Interim mitigation

Upgrade to Firefox 3.5.11/3.6.7, Thunderbird 3.0.6/3.1.1, SeaMonkey 2.0.6 or later; or remove these legacy products from the environment if patching is not feasible.

Recommended fix High confidence

Firefox 3.5.11+ or 3.6.7+ | Thunderbird 3.0.6+ or 3.1.1+ | SeaMonkey 2.0.6+

  1. Identify the exact Mozilla product and version currently installed (Firefox, Thunderbird, or SeaMonkey)
  2. For Firefox 3.5.x users: upgrade to Firefox 3.5.11 or later (or migrate to a supported Firefox release)
  3. For Firefox 3.6.x users: upgrade to Firefox 3.6.7 or later (or migrate to a supported Firefox release)
  4. For Thunderbird 3.0.x users: upgrade to Thunderbird 3.0.6 or later
  5. For Thunderbird 3.1.x users: upgrade to Thunderbird 3.1.1 or later
  6. For SeaMonkey 1.x users: upgrade to SeaMonkey 2.0.6 or later
  7. For SeaMonkey 2.0.x users: upgrade to SeaMonkey 2.0.6 or later
  8. After upgrading, verify the new version is running and test critical functionality
Caveat These are very old 2010 versions; upgrading may cause compatibility issues with modern systems and web content; consider migrating to a currently supported Firefox/Thunderbird release branch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-2752 — 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-2752 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