dbcve.org
FirefoxWeb browser · Mozilla

CVE-2011-0084

HIGH · 10.0 CVSS v2.0 Published 2011-08-18
Fix available
A fix is available. Upgrade to after 3.6.19 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 SVGTextElement.getCharNumAtPosition function in Mozilla Firefox before 3.6.20, and 4.x through 5; Thunderbird 3.x before 3.1.12 and other versions before 6; SeaMonkey 2.x before 2.3; and possibly other products does not properly handle SVG text, which allows remote attackers to execute arbitrary code via unspecified vectors that lead to a "dangling pointer."

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

A dangling pointer vulnerability in the SVGTextElement.getCharNumAtPosition function in Mozilla Firefox, Thunderbird, and SeaMonkey allows remote attackers to execute arbitrary code via specially crafted SVG text content. The vulnerability stems from improper handling of SVG text that leads to a use-after-free condition where memory is accessed after being freed.

MitigationUpdate affected Mozilla products to the patched versions (Firefox 3.6.20+/6+, Thunderbird 3.1.12+/6+, SeaMonkey 2.3+) or enable automatic updates to receive security patches. Deploy through enterprise patch management where applicable.

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.6.19= 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.5= 1.5.0.1
SeamonkeyApplication
Affected:= 2.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.8= 2.0.9= 2.0.10= 2.0.11
ThunderbirdApplication
Affected:= 3.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5= 3.0.6= 3.0.7= 3.0.8= 3.0.9= 3.0.10= 3.0.11

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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 the installed Mozilla product
    Check if Firefox, Thunderbird, or SeaMonkey is installed by looking in the application's About menu or checking the program files directory
    Affected if Any of the three products (Firefox, Thunderbird, or SeaMonkey) is installed
  2. Determine the installed version of Firefox
    In Firefox, go to Help > About Mozilla Firefox. The version number will be displayed in the window that opens
    Affected if The version is 3.6.19 or lower, or any of 1.0.x through 1.5.0.1 versions listed in the affected range
  3. Determine the installed version of Thunderbird
    In Thunderbird, go to Help > About Mozilla Thunderbird. The version number will be displayed in the window that opens
    Affected if The version is any of the 3.0.x versions listed (3.0 through 3.0.11)
  4. Determine the installed version of SeaMonkey
    In SeaMonkey, go to Help > About SeaMonkey. The version number will be displayed in the window that opens
    Affected if The version is any of the 2.0.x versions listed (2.0 through 2.0.11)
  5. Verify SVG rendering is enabled
    In Firefox, type 'about:config' in the address bar, then search for 'svg' to confirm SVG rendering is not disabled
    Affected if SVG rendering is enabled (the vulnerability requires SVG content to be processed)

The environment is affected if any of Firefox (versions <= 3.6.19 or 1.0-1.5.0.1), Thunderbird (versions 3.0-3.0.11), or SeaMonkey (versions 2.0-2.0.11) is installed with SVG rendering enabled.

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

Update affected Mozilla products to the patched versions (Firefox 3.6.20+/6+, Thunderbird 3.1.12+/6+, SeaMonkey 2.3+) or enable automatic updates to receive security patches. Deploy through enterprise patch management where applicable.

Recommended fix High confidence

Firefox 3.6.20 / Firefox 6+; SeaMonkey 2.3+; Thunderbird 3.1.12 / Thunderbird 6+

  1. Identify which affected product (Firefox, SeaMonkey, or Thunderbird) is installed on the system
  2. For Firefox: Check the current version via Help > About Firefox
  3. For SeaMonkey: Check the current version via Help > About SeaMonkey
  4. For Thunderbird: Check the current version via Help > About Thunderbird
  5. Download and install Firefox 3.6.20 or later, or Firefox 6 or later from mozilla.org
  6. OR download and install SeaMonkey 2.3 or later from mozilla.org
  7. OR download and install Thunderbird 3.1.12 or later, or Thunderbird 6 or later from mozilla.org
  8. Restart the application after upgrade
Caveat Upgrading from Firefox 3.6.x to Firefox 6+ may introduce compatibility issues with older extensions and plugins; Thunderbird 3.x to 6+ may change UI and plugin compatibility

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-2011-0084 — 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-2011-0084 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