dbcve.org
FirefoxWeb browser · Mozilla

CVE-2013-5604

HIGH · 9.3 CVSS v2.0 Published 2013-10-30
Fix available
A fix is available. Upgrade to after 24.0.1 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
The txXPathNodeUtils::getBaseURI function in the XSLT processor 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 does not properly initialize data, which allows remote attackers to execute arbitrary code or cause a denial of service (stack-based buffer overflow and application crash) via crafted documents.

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

The txXPathNodeUtils::getBaseURI function in Mozilla's XSLT processor fails to properly initialize data structures, leading to a stack-based buffer overflow when processing specially crafted XSLT documents. This memory corruption vulnerability can be triggered remotely via malicious documents, potentially allowing arbitrary code execution.

MitigationApply vendor patches by updating affected products to Firefox 25.0+, Firefox ESR 17.0.10+/24.1+, Thunderbird 24.1+/ESR 17.0.10+, or SeaMonkey 2.22+. Avoid opening untrusted XSLT/XML documents until updates are applied.

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:= 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= 17.0.9= 24.0= 24.0.1
Thunderbird EsrApplication
Affected:= 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= 17.0.9
SeamonkeyApplication
Affected:<= 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
ThunderbirdApplication
Affected:<= 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

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

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, Thunderbird, or SeaMonkey is installed. On Windows, look in Program Files; on Linux, check /usr/lib/firefox or use 'which firefox'; on macOS check /Applications.
    Affected if Any of Firefox, Thunderbird, or SeaMonkey is installed
  2. Determine Firefox version
    In Firefox, go to Help > About Firefox, or enter 'about:support' in the address bar, or run 'firefox --version' from command line
    Affected if Version is 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, 17.0.9, 24.0, or 24.0.1
  3. Determine Thunderbird version
    In Thunderbird, go to Help > About Thunderbird, or run 'thunderbird --version' from command line
    Affected if Version is 17.0 through 17.0.9, 24.0, or any version <= 24.0.1
  4. Determine SeaMonkey version
    In SeaMonkey, go to Help > About SeaMonkey, or run 'seamonkey --version' from command line
    Affected if Version is 2.0 through 2.0.10, or any version <= 2.22

The system is affected if Firefox 17.0-17.0.9, 24.0-24.0.1, Thunderbird 17.0-17.0.9, 24.0-24.0.1 (or <=24.0.1), or SeaMonkey <=2.22 / 2.0-2.0.10 is installed and the XSLT processor feature is in use (enabled by default).

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

Apply vendor patches by updating affected products to Firefox 25.0+, Firefox ESR 17.0.10+/24.1+, Thunderbird 24.1+/ESR 17.0.10+, or SeaMonkey 2.22+. Avoid opening untrusted XSLT/XML documents until updates are applied.

Recommended fix High confidence

Firefox 25.0+, Firefox ESR 17.0.10+, Firefox ESR 24.1+, Thunderbird 24.1+, Thunderbird ESR 17.0.10+, SeaMonkey 2.22+

  1. 1. Identify the installed Mozilla product (Firefox, Thunderbird, SeaMonkey) and current version using the application's 'About' menu or command line (e.g., 'firefox --version')
  2. 2. For Firefox 17.x: Upgrade to Firefox 17.0.10 or later, or migrate to Firefox 24.1 or later, or the latest stable Firefox release
  3. 3. For Firefox ESR 17.x: Upgrade to Firefox ESR 17.0.10 or later
  4. 4. For Firefox ESR 24.x: Upgrade to Firefox ESR 24.1 or later
  5. 5. For Thunderbird 17.x: Upgrade to Thunderbird 24.1 or later
  6. 6. For Thunderbird ESR 17.x: Upgrade to Thunderbird ESR 17.0.10 or later
  7. 7. For Thunderbird <= 24.0.1: Upgrade to Thunderbird 24.1 or later
  8. 8. For SeaMonkey <= 2.22: Upgrade to SeaMonkey 2.22 or later
Caveat Upgrading to newer major versions (e.g., from Firefox 17 to 25+) may introduce compatibility issues with older extensions or plugins; test in a non-production environment first

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-2013-5604 — 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-5604 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