CVE-2013-5601
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 · uneditedUse-after-free vulnerability in the nsEventListenerManager::SetEventHandler function in Mozilla Firefox before 25.0, Firefox ESR 17.x before 17.0.10 and 24.x before 24.1, Thunderbird before 24.1, Thunderbird ESR 17.x before 17.0.10, and SeaMonkey before 2.22 allows remote attackers to execute arbitrary code via vectors related to a memory allocation through the garbage collection (GC) API.
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 confidenceUse-after-free vulnerability in Mozilla's nsEventListenerManager::SetEventHandler function where memory allocated through the garbage collection API is freed while still being referenced. Attackers can exploit this to execute arbitrary code by triggering specific memory allocation patterns through the GC API.
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<= 24.0= 19.0= 19.0.1= 19.0.2= 20.0= 20.0.1= 21.0= 22.0= 23.0= 23.0.1= 17.0= 17.0.1<= 2.22= 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<= 24.0.1= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4= 17.0.5= 17.0.6= 17.0.7= 17.0.8= 24.0= 17.0.9= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4= 17.0.5= 17.0.6= 17.0.7= 17.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Firefox versionNavigate to Firefox menu > Help > About Firefox, or enter 'about:support' in the address bar to view the version numberAffected if The installed version is 17.0, 17.0.1, 19.0, 19.0.1, 19.0.2, 20.0, 20.0.1, 21.0, 22.0, 23.0, 23.0.1, 24.0, or any version lower than 24.0
-
Check SeaMonkey versionNavigate to SeaMonkey menu > Help > About SeaMonkey to view the version numberAffected if The installed version is 2.0 through 2.0.10, or any version 2.22 or lower
-
Check Thunderbird versionNavigate to Thunderbird menu > Help > About Thunderbird to view the version numberAffected if The installed version is 17.0 through 17.0.8, 24.0, 24.0.1, or any version lower than 24.0.1
-
Check Thunderbird ESR versionNavigate to Thunderbird menu > Help > About Thunderbird to view the version number, ESR status is typically displayed in the about windowAffected if The installed version is 17.0 through 17.0.9
A user is affected if they are running any of the vulnerable Firefox, SeaMonkey, Thunderbird, or Thunderbird ESR versions listed in the affected version ranges.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate affected Mozilla products to patched versions: Firefox 25.0+, Firefox ESR 17.0.10+/24.1+, Thunderbird 24.1+/Thunderbird ESR 17.0.10+, or SeaMonkey 2.22+.
Firefox: 25.0 or later (or ESR 17.0.10+ / ESR 24.1+); Thunderbird: 24.1 or later (or ESR 17.0.10+); SeaMonkey: 2.22 or later
- 1. Identify the exact Mozilla product and version currently installed (Firefox, Firefox ESR, Thunderbird, Thunderbird ESR, or SeaMonkey)
- 2. Download the appropriate fixed version from the official Mozilla website or your organization's software repository
- 3. Close all instances of the affected Mozilla product
- 4. Install the fixed version: For Firefox, upgrade to 25.0 or later; For Firefox ESR 17.x, upgrade to 17.0.10 or later; For Firefox ESR 24.x, upgrade to 24.1 or later; For Thunderbird, upgrade to 24.1 or later; For Thunderbird ESR 17.x, upgrade to 17.0.10 or later; For SeaMonkey, upgrade to 2.22 or later
- 5. Restart the application after installation
- 6. Verify the installed version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2013-5601 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-5601 in production — separate from our analysis above.
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.
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.
- 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