CVE-2013-5600
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 nsIOService::NewChannelFromURIWithProxyFlags 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 involving a blob: URL.
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 nsIOService::NewChannelFromURIWithProxyFlags allows remote attackers to execute arbitrary code via specially crafted blob: URL vectors in Mozilla Firefox before 25.0, Firefox ESR 17.x/24.x, Thunderbird before 24.1, Thunderbird ESR 17.x, and SeaMonkey before 2.22.
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<= 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.8<= 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.10CVSS 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.
-
Identify the installed Mozilla productCheck which Mozilla application is installed on the system: Firefox, Thunderbird, or SeaMonkey. On Windows, check Add/Remove Programs or the application executable properties. On Linux, check the package manager or application menu. On macOS, check /Applications folder or the app bundle info.Affected if Any of the affected products (Firefox, Thunderbird, Thunderbird ESR, SeaMonkey) are installed
-
Determine the installed Firefox versionIn Firefox, navigate to Help > About Firefox, or enter 'about:support' in the address bar. The version number is displayed at the top of the page.Affected if The version is 24.0 or lower, or matches any of these specific versions: 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
-
Determine the installed Thunderbird versionIn Thunderbird, navigate to Help > About Thunderbird. The version number is displayed in the dialog window.Affected if The version is 24.0.1 or lower, or matches any of these specific versions: 17.0 through 17.0.8 (including all point releases), 24.0
-
Determine the installed SeaMonkey versionIn SeaMonkey, navigate to Help > About SeaMonkey. The version number is displayed in the dialog window.Affected if The version is 2.22 or lower, or matches any of these specific versions: 2.0 through 2.0.10 (including all point releases)
If any of the identified Mozilla products match the affected version ranges listed for CVE-2013-5600, the environment is potentially vulnerable to the use-after-free flaw via blob: URL vectors.
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 · scopedDeploy vendor-supplied patches by updating all affected Mozilla products (Firefox, Firefox ESR, Thunderbird, Thunderbird ESR, SeaMonkey) to the patched versions specified in Mozilla security advisories.
Firefox 25.0 / Firefox ESR 17.0.10 or 24.1 / Thunderbird 24.1 / Thunderbird ESR 17.0.10 / SeaMonkey 2.22
- Identify which Mozilla product (Firefox, Thunderbird, Thunderbird ESR, or SeaMonkey) is installed and note its current version
- For Firefox users: Upgrade to Firefox 25.0 or later (or Firefox ESR 24.1+ for extended support)
- For Thunderbird users: Upgrade to Thunderbird 24.1 or later
- For Thunderbird ESR users: Upgrade to Thunderbird ESR 17.0.10 or later
- For SeaMonkey users: Upgrade to SeaMonkey 2.22 or later
- Download the appropriate updated version from the official Mozilla website (mozilla.org) or use the built-in update mechanism (Help > About > Check for Updates)
- Restart the application after the update is complete
- Verify the installed version matches or exceeds 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-5600 — 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-5600 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