dbcve.org
FirefoxWeb browser · Mozilla

CVE-2011-0083

HIGH · 10.0 CVSS v2.0 Published 2011-06-30
Fix available
A fix is available. Upgrade to after 3.6.17 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
Use-after-free vulnerability in the nsSVGPathSegList::ReplaceItem function in the implementation of SVG element lists in Mozilla Firefox before 3.6.18, Thunderbird before 3.1.11, and SeaMonkey through 2.0.14 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via vectors involving a user-supplied callback.

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

Use-after-free vulnerability in the nsSVGPathSegList::ReplaceItem function within Mozilla's SVG element list implementation. Attackers can trigger the vulnerability through user-supplied callbacks, causing a crash (DoS) or potentially achieving arbitrary code execution by freeing memory that is later accessed.

MitigationApply vendor patches: update Firefox to 3.6.18+, Thunderbird to 3.1.11+, or SeaMonkey to 2.0.14 or later. Prioritize patching given the CVSS 10 severity and proof-of-concept exploit availability.

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.17= 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:= 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= 1.1.1
ThunderbirdApplication
Affected:<= 3.1.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

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 installed Mozilla product
    Check if Firefox, SeaMonkey, or Thunderbird is installed by looking at program files or running the application. Note the product name.
    Affected if Any of the three affected products is installed
  2. Determine Firefox version
    Run 'firefox --version' from command line or check Help > About Firefox. Compare the version number against: 1.0 through 1.0.8, 1.5 through 1.5.0.1, or 3.6.17 and below.
    Affected if Firefox version matches any of the listed affected versions
  3. Determine SeaMonkey version
    Run 'seamonkey --version' from command line or check Help > About SeaMonkey. Compare against: 1.0 through 1.0.9, 1.1, or 1.1.1.
    Affected if SeaMonkey version matches any of the listed affected versions
  4. Determine Thunderbird version
    Run 'thunderbird --version' from command line or check Help > About Thunderbird. Compare against: 0.1 through 0.8, or 3.1.10 and below.
    Affected if Thunderbird version matches any of the listed affected versions
  5. Confirm SVG usage context
    This vulnerability is in the core SVG rendering engine (nsSVGPathSegList). The flaw is triggerable when the application processes SVG path data with user-supplied callback modifications.
    Affected if The affected product version is identified and the application processes SVG content

A user is affected if they are running any version of Firefox <= 3.6.17 or 1.0.x/1.5.x, SeaMonkey 1.0.x/1.1.x, or Thunderbird <= 3.1.10 or 0.x, as these contain the vulnerable nsSVGPathSegList::ReplaceItem function.

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

Apply vendor patches: update Firefox to 3.6.18+, Thunderbird to 3.1.11+, or SeaMonkey to 2.0.14 or later. Prioritize patching given the CVSS 10 severity and proof-of-concept exploit availability.

Recommended fix High confidence

Firefox 3.6.18+ / Thunderbird 3.1.11+ / SeaMonkey 2.0.14+

  1. Upgrade Firefox to version 3.6.18 or later (preferably the latest supported Firefox ESR or current release)
  2. Upgrade Thunderbird to version 3.1.11 or later (preferably the latest supported Thunderbird ESR or current release)
  3. Upgrade SeaMonkey to version 2.0.14 or later (preferably the latest supported SeaMonkey version)
  4. For Firefox 1.0.x and SeaMonkey 1.0.x branches (which are obsolete), migrate to a supported version as these older releases are no longer patched
Caveat Firefox 3.6.x reached end of life; migrating to modern Firefox may require add-on compatibility changes and user profile adjustments

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