dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-3769

HIGH · 9.3 CVSS v2.0 Published 2010-12-10
Fix available
A fix is available. Upgrade to after 3.5.15 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
The line-breaking implementation in Mozilla Firefox before 3.5.16 and 3.6.x before 3.6.13, Thunderbird before 3.0.11 and 3.1.x before 3.1.7, and SeaMonkey before 2.0.11 on Windows does not properly handle long strings, which allows remote attackers to execute arbitrary code via a crafted document.write call that triggers a buffer over-read.

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

Buffer over-read vulnerability in Mozilla Firefox, Thunderbird, and SeaMonkey's Windows line-breaking implementation. A crafted document.write() call with long strings triggers the buffer over-read, allowing remote arbitrary code execution.

MitigationUpgrade affected browsers to Firefox 3.5.16+/3.6.13+, Thunderbird 3.0.11+/3.1.7+, or SeaMonkey 2.0.11+ to patch the vulnerability.

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.15= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.6.1= 0.7= 0.7.1= 0.8= 0.9
ThunderbirdApplication
Affected:<= 3.0.10= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.7= 0.7.1= 0.7.2= 0.7.3= 0.8
SeamonkeyApplication
Affected:<= 2.0.10= 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 Mozilla product
    Check for Firefox, Thunderbird, or SeaMonkey installation. On Windows, look in Program Files or check application menus Help > About. On Linux, check /usr/bin/firefox, /usr/bin/thunderbird, or /usr/bin/seamonkey.
    Affected if Any of the three products (Firefox, Thunderbird, SeaMonkey) is installed
  2. Determine product version
    Open the application and navigate to Help > About (Firefox/Thunderbird) or Help > About SeaMonkey. Record the full version number shown.
    Affected if Version is 0.1 through 3.5.15 for Firefox; 0.1 through 3.0.10 or 3.1.x below 3.1.7 for Thunderbird; 1.0 through 1.1 or 2.0.x below 2.0.11 for SeaMonkey
  3. Confirm Windows platform
    Verify the operating system is Windows, as the vulnerability exists specifically in the Windows line-breaking implementation.
    Affected if Running on Windows (the flaw is in Windows-specific line-breaking code)
  4. Check JavaScript enabled status
    The exploit uses document.write() which requires JavaScript. In browser settings, verify if JavaScript is enabled (Tools > Options > Content in Firefox, or Edit > Preferences > Privacy & Security > Scripting in Thunderbird).
    Affected if JavaScript is enabled in the browser settings

You are affected if you run Firefox <= 3.5.15, Thunderbird <= 3.0.10, or SeaMonkey <= 2.0.10 on Windows with JavaScript enabled and the installed version matches the specific affected ranges listed.

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.5.15
Interim mitigation

Upgrade affected browsers to Firefox 3.5.16+/3.6.13+, Thunderbird 3.0.11+/3.1.7+, or SeaMonkey 2.0.11+ to patch the vulnerability.

Recommended fix High confidence

Firefox 3.5.16+/3.6.13+, Thunderbird 3.0.11+/3.1.7+, or SeaMonkey 2.0.11+

  1. 1. Identify the currently installed Mozilla product (Firefox, Thunderbird, or SeaMonkey) and its exact version number
  2. 2. Close all instances of the affected application
  3. 3. For Firefox: Download and install version 3.5.16 or later, or version 3.6.13 or later from mozilla.org
  4. 4. For Thunderbird: Download and install version 3.0.11 or later, or version 3.1.7 or later from mozilla.org
  5. 5. For SeaMonkey: Download and install version 2.0.11 or later from mozilla.org
  6. 6. Restart the application after installation
  7. 7. Verify the installed version matches or exceeds the fixed versions specified
Caveat These are very old versions from 2010; upgrading to modern supported releases (Firefox ESR 115+, Thunderbird 115+) is recommended for ongoing security support

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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