FirefoxWeb browser · Mozilla

CVE-2013-5602

HIGH · 10.0 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 Worker::SetEventListener function in the Web workers implementation 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 or cause a denial of service (memory corruption) via vectors related to direct proxies.

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 Worker::SetEventListener function in Mozilla's Web Workers implementation contains a memory corruption vulnerability when handling direct proxy objects. This allows remote attackers to potentially execute arbitrary code or cause a denial of service via specially crafted JavaScript proxy objects passed to worker event listeners.

MitigationUpdate affected Mozilla products to the patched versions: Firefox 25.0 or later, Firefox ESR 17.0.10/24.1 or later, Thunderbird 24.1 or later, Thunderbird ESR 17.0.10 or later, or SeaMonkey 2.22 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:= 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
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
Thunderbird EsrApplication
Affected:= 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
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

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 installed Mozilla product
    Open the application and navigate to Help > About (Firefox/Thunderbird) or Help > About SeaMonkey. Alternatively, check the application executable or package information.
    Affected if The product is Mozilla Firefox, Thunderbird, or SeaMonkey
  2. Determine the installed version number
    Note the full version number displayed in the About dialog (e.g., 17.0.7, 24.0.1, 2.22)
    Affected if Version cannot be determined or is not displayed
  3. Compare version against Firefox affected range
    If the product is Firefox, check 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
    Affected if Firefox version matches any of these exact versions
  4. Compare version against Thunderbird affected range
    If the product is Thunderbird, check if version is 17.0 through 17.0.9 (any 17.x), or 24.0, or 24.0.1, or any version <= 24.0.1
    Affected if Thunderbird version is 17.0-17.0.9, 24.0, 24.0.1, or <= 24.0.1
  5. Compare version against SeaMonkey affected range
    If the product is SeaMonkey, check if version is 2.0 through 2.0.10 (any 2.0.x), or any version <= 2.22
    Affected if SeaMonkey version is 2.0-2.0.10 or <= 2.22

The environment is affected if a Mozilla product (Firefox, Thunderbird, or SeaMonkey) is installed and its version matches any of the specific versions or ranges listed in the affected products and versions.

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

Update affected Mozilla products to the patched versions: Firefox 25.0 or later, Firefox ESR 17.0.10/24.1 or later, Thunderbird 24.1 or later, Thunderbird ESR 17.0.10 or later, or SeaMonkey 2.22 or later.

Recommended fix High confidence

Firefox 25.0+ (or ESR 17.0.10+/24.1+), Thunderbird 24.1+ (or ESR 17.0.10+), SeaMonkey 2.22+

  1. 1. Check current installed version of Firefox, Thunderbird, or SeaMonkey
  2. 2. Back up important user data (bookmarks, emails, settings)
  3. 3. For Firefox: Upgrade to version 25.0 or later (or Firefox ESR 17.0.10+/24.1+)
  4. 4. For Thunderbird: Upgrade to version 24.1 or later (or Thunderbird ESR 17.0.10+)
  5. 5. For SeaMonkey: Upgrade to version 2.22 or later
  6. 6. Restart the application after upgrading
  7. 7. Verify the updated version is installed
Caveat Upgrading may cause incompatibility with older extensions or add-ons; 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
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-5602 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