dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-1202

HIGH · 9.3 CVSS v2.0 Published 2010-06-24
Fix available
A fix is available. Upgrade to after 3.0.4 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
Multiple unspecified vulnerabilities in the JavaScript engine in Mozilla Firefox 3.5.x before 3.5.10 and 3.6.x before 3.6.4, Thunderbird before 3.0.5, and SeaMonkey before 2.0.5 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.

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

Multiple memory corruption vulnerabilities in the JavaScript engine of Mozilla Firefox 3.5.x before 3.5.10, Firefox 3.6.x before 3.6.4, Thunderbird before 3.0.5, and SeaMonkey before 2.0.5 that could allow remote attackers to execute arbitrary code or cause denial of service via unknown JavaScript vectors.

MitigationUpdate affected Mozilla products to the patched versions (Firefox 3.5.10/3.6.4, Thunderbird 3.0.5, SeaMonkey 2.0.5) or migrate to currently supported versions.

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= 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.6= 3.6.2= 3.6.3
SeamonkeyApplication
Affected:<= 2.0.4= 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
ThunderbirdApplication
Affected:<= 3.0.4= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.7= 0.8= 0.9= 1.0= 1.0.2

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 Mozilla product
    Open the application and go to Help > About (Firefox/Thunderbird) or Help > About SeaMonkey. Alternatively, check the application executable properties or use 'firefox --version', 'thunderbird --version', or 'seamonkey --version' in command line.
    Affected if The product is Firefox, SeaMonkey, or Thunderbird and the version matches the affected ranges
  2. Check Firefox version
    In Firefox, navigate to Help > About Firefox, or run 'firefox --version'. The version string will be in the format 3.5.x or 3.6.x.
    Affected if Version is 3.5.0 through 3.5.9, or 3.6.0, 3.6.2, or 3.6.3 (not 3.5.10 or later, not 3.6.4 or later)
  3. Check SeaMonkey version
    In SeaMonkey, navigate to Help > About SeaMonkey, or run 'seamonkey --version'. The version string will be in the format 1.x or 2.0.x.
    Affected if Version is 1.0.x through 1.1.x, or 2.0.0 through 2.0.4 (not 2.0.5 or later)
  4. Check Thunderbird version
    In Thunderbird, navigate to Help > About Thunderbird, or run 'thunderbird --version'. The version string will be in the format 0.x, 1.0.x, or 3.0.x.
    Affected if Version is 0.1 through 1.0.2, or 3.0.0 through 3.0.4 (not 3.0.5 or later)

If the installed Mozilla product is Firefox 3.5.x before 3.5.10, Firefox 3.6.x before 3.6.4, SeaMonkey 2.0.4 or earlier/1.x, or Thunderbird 3.0.4 or earlier/0.x-1.0.x, the environment is affected by this vulnerability.

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 3.0.4
Interim mitigation

Update affected Mozilla products to the patched versions (Firefox 3.5.10/3.6.4, Thunderbird 3.0.5, SeaMonkey 2.0.5) or migrate to currently supported versions.

Recommended fix High confidence

Firefox: 3.5.10+ (or 3.6.4+); SeaMonkey: 2.0.5+; Thunderbird: 3.0.5+

  1. Identify which Mozilla product is affected (Firefox, SeaMonkey, or Thunderbird)
  2. Check the current installed version of the application
  3. Close all instances of the affected application
  4. Download the fixed version from the official Mozilla website or use your system's package manager to upgrade
  5. For Firefox: upgrade to version 3.5.10 or later (or 3.6.4+ for the 3.6.x branch)
  6. For SeaMonkey: upgrade to version 2.0.5 or later
  7. For Thunderbird: upgrade to version 3.0.5 or later
  8. Restart the application and verify the update was successful
Caveat Legacy extension compatibility may be affected when upgrading to newer major versions; test critical extensions before production deployment

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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