FirefoxWeb browser · Mozilla

CVE-2010-1196

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

NVD · unedited

Integer overflow in the nsGenericDOMDataNode::SetTextInternal function 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 allows remote attackers to execute arbitrary code via a DOM node with a long text value that triggers a heap-based buffer overflow.

Technical summary

dbcve analysis · high confidence

Integer overflow in nsGenericDOMDataNode::SetTextInternal allows remote attackers to cause a heap-based buffer overflow via a DOM node containing an excessively long text value, enabling arbitrary code execution.

MitigationUpgrade to Firefox 3.5.10+/3.6.4+, Thunderbird 3.0.5+, or SeaMonkey 2.0.5+; consider disabling JavaScript or restricting untrusted content until patches are deployed.

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

Affected products & versions

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

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?

dbcve checks

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

Check Firefox version

Run 'firefox --version' or look in Help > About Firefox

Affected if Version is 3.5.0 through 3.5.9, 3.6.0 through 3.6.3, or any 3.5.x build listed in the affected versions
Check SeaMonkey version

Run 'seamonkey --version' or look in Help > About SeaMonkey

Affected if Version is 1.0.x through 1.1, or 2.0.4 or earlier
Check Thunderbird version

Run 'thunderbird --version' or look in Help > About Thunderbird

Affected if Version is 3.0.4 or earlier, or 0.1 through 1.0.2 inclusive

You are affected if any installed Mozilla product (Firefox, SeaMonkey, Thunderbird) matches one of the specific version numbers or ranges listed in the affected products list.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 3.0.4

Interim mitigation

Upgrade to Firefox 3.5.10+/3.6.4+, Thunderbird 3.0.5+, or SeaMonkey 2.0.5+; consider disabling JavaScript or restricting untrusted content until patches are deployed.

Recommended fix High confidence

Firefox 3.5.10+/3.6.4+, Thunderbird 3.0.5+, or SeaMonkey 2.0.5+ depending on product

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.10 or later, or migrate to Firefox 3.6.4 or later
3. For Firefox 3.6.x users: Upgrade to Firefox 3.6.4 or later
4. For Thunderbird users: Upgrade to Thunderbird 3.0.5 or later
5. For SeaMonkey users: Upgrade to SeaMonkey 2.0.5 or later
6. After upgrade, verify the installed version matches the fixed release

Caveat Older extensions or add-ons may be incompatible with newer major versions; test in non-production environment first

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

Fix this in Firefox Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

18.0 hours of engineering $3,200

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2010-1196?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 3.0.4 or later

Severity 9.3 High

Exploit likelihood EPSS, next 30 days 4.9%

Affects: Firefox

Remediation

A high-priority fix

Fix this in Firefox 18 hrs · Moderate

Typical engagement from $3,200

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2010-1196 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References