dbcve.org
FirefoxWeb browser · Mozilla

CVE-2013-0754

HIGH · 9.3 CVSS v2.0 Published 2013-01-13
Fix available
A fix is available. Upgrade to 2.15 / 10.0.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 ListenerManager implementation in Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderbird ESR 10.x before 10.0.12 and 17.x before 17.0.2, and SeaMonkey before 2.15 allows remote attackers to execute arbitrary code via vectors involving the triggering of garbage collection after memory allocation for listener objects.

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
How this class of weakness works · CWE-416

Memory is used after it has been freed, so its contents — now potentially attacker-controlled — drive the program's behaviour. With careful heap grooming this becomes code execution. The fix requires disciplined ownership of memory and often a targeted rework of the object lifecycle.

General guidance for the use after free class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:< 18.0>= 10.0, < 10.0.12>= 17.0, < 17.0.2
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0
Enterprise Linux EusOperating system
Affected:= 5.9= 6.3
Enterprise Linux ServerOperating system
Affected:= 5.0= 6.0
Enterprise Linux Server AusOperating system
Affected:= 5.9
Enterprise Linux WorkstationOperating system
Affected:= 5.0= 6.0
Ubuntu LinuxOperating system
Affected:= 10.04= 11.10= 12.04= 12.10
SeamonkeyApplication
Affected:< 2.15

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

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 2.15 / 10.0.12 / 17.0.2 or later
Fixed in 2.1510.0.1217.0.2
Vendor patch bugzilla.mozilla.org →
Recommended fix High confidence

Firefox 18.0 (or Firefox ESR 10.0.12 / ESR 17.0.2); Seamonkey 2.15

  1. 1. Identify the currently installed Firefox or Seamonkey version by navigating to Help > About [Product Name]
  2. 2. For Firefox users: If running a release version < 18.0, upgrade to Firefox 18.0 or later
  3. 3. For Firefox ESR users: If running 10.x, upgrade to Firefox ESR 10.0.12 or later; if running 17.x, upgrade to Firefox ESR 17.0.2 or later
  4. 4. For Seamonkey users: If running a version < 2.15, upgrade to Seamonkey 2.15 or later
  5. 5. Restart the browser after upgrade
  6. 6. Verify the version by checking Help > About to confirm the new version is installed
Caveat Users of Firefox 10.x ESR and 17.x ESR should upgrade to the specified ESR versions to maintain extended support; some older add-ons may be incompatible with newer versions

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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