dbcve.org
FirefoxWeb browser · Mozilla

CVE-2012-1951

HIGH · 10.0 CVSS v2.0 Published 2012-07-18
Fix available
A fix is available. Upgrade to after 2.10 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 nsSMILTimeValueSpec::IsEventBased function in Mozilla Firefox 4.x through 13.0, Firefox ESR 10.x before 10.0.6, Thunderbird 5.0 through 13.0, Thunderbird ESR 10.x before 10.0.6, and SeaMonkey before 2.11 allows remote attackers to cause a denial of service (heap memory corruption) or possibly execute arbitrary code by interacting with objects used for SMIL Timing.

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 nsSMILTimeValueSpec::IsEventBased function allows remote attackers to cause heap memory corruption or potentially execute arbitrary code by interacting with SMIL Timing objects in affected Mozilla products.

MitigationUpdate vulnerable installations to Firefox 13.0, Firefox ESR 10.0.6, Thunderbird 13.0, Thunderbird ESR 10.0.6, SeaMonkey 2.11 or later.

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:= 4.0= 4.0.1= 5.0= 5.0.1= 6.0= 6.0.1= 6.0.2= 7.0= 7.0.1= 8.0= 8.0.1= 9.0
ThunderbirdApplication
Affected:= 5.0= 6.0= 6.0.1= 6.0.2= 7.0= 7.0.1= 8.0= 9.0= 9.0.1= 10.0= 10.0.1= 10.0.2
Thunderbird EsrApplication
Affected:= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.0.5
SeamonkeyApplication
Affected:<= 2.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
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 Help > About in the application menu, or run: Firefox: 'firefox --version', Thunderbird: 'thunderbird --version', SeaMonkey: 'seamonkey --version'
    Affected if The version matches any of: Firefox 4.0, 4.0.1, 5.0, 5.0.1, 6.0, 6.0.1, 6.0.2, 7.0, 7.0.1, 8.0, 8.0.1, 9.0; Thunderbird 5.0, 6.0, 6.0.1, 6.0.2, 7.0, 7.0.1, 8.0, 9.0, 9.0.1, 10.0, 10.0.1, 10.0.2; Thunderbird ESR 10.0, 10.0.1, 10.0.2, 10.0.3, 10.0.4, 10.0.5; SeaMonkey 1.0 through 1.1.x, or SeaMonkey 2

The environment is affected if the installed Firefox, Thunderbird, or SeaMonkey version is among those listed AND SMIL timing features are being used in web content.

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

Update vulnerable installations to Firefox 13.0, Firefox ESR 10.0.6, Thunderbird 13.0, Thunderbird ESR 10.0.6, SeaMonkey 2.11 or later.

Recommended fix High confidence

Upgrade to Firefox 13.0.1+, Firefox ESR 10.0.6+, Thunderbird 13.0.1+, Thunderbird ESR 10.0.6+, or SeaMonkey 2.11+ (depending on product in use)

  1. 1. Determine the currently installed Firefox, Thunderbird, or SeaMonkey version by navigating to Help > About [Product Name]
  2. 2. If Firefox is installed and version is 4.0 through 13.0, upgrade to Firefox 13.0.1 or later
  3. 3. If Firefox ESR is installed and version is 10.0.x where x < 6, upgrade to Firefox ESR 10.0.6 or later
  4. 4. If Thunderbird is installed and version is 5.0 through 13.0, upgrade to Thunderbird 13.0.1 or later
  5. 5. If Thunderbird ESR is installed and version is 10.0.x where x < 6, upgrade to Thunderbird ESR 10.0.6 or later
  6. 6. If SeaMonkey is installed and version is <= 2.10, upgrade to SeaMonkey 2.11 or later
  7. 7. Restart the application after upgrading
Caveat These are stable release upgrades; ensure compatibility with any installed add-ons before upgrading

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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