dbcve.org
FirefoxWeb browser · Mozilla

CVE-2013-1718

HIGH · 10.0 CVSS v2.0 Published 2013-09-18
Fix available
A fix is available. Upgrade to after 23.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
Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 24.0, Firefox ESR 17.x before 17.0.9, Thunderbird before 24.0, Thunderbird ESR 17.x before 17.0.9, and SeaMonkey before 2.21 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.

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

Memory corruption vulnerability in the Mozilla browser engine affecting Firefox before 24.0, Firefox ESR 17.x before 17.0.9, Thunderbird before 24.0, Thunderbird ESR 17.x before 17.0.9, and SeaMonkey before 2.21. Allows remote attackers to potentially execute arbitrary code via unknown vectors.

MitigationUpgrade to Firefox 24.0+, Thunderbird 24.0+, SeaMonkey 2.21+, or Firefox/Thunderbird ESR 17.0.9+. In enterprise environments, test and deploy patches through standard software distribution mechanisms.

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:<= 23.0.1= 19.0= 19.0.1= 19.0.2= 20.0= 20.0.1= 21.0= 22.0= 23.0= 17.0= 17.0.1= 17.0.2
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
ThunderbirdApplication
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.20= 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 the installed Mozilla product
    Open the application and navigate to Help > About (Firefox/Thunderbird) or Help > About SeaMonkey. The product name and version will be displayed in the About window.
    Affected if Any of Firefox, Thunderbird, or SeaMonkey is installed
  2. Confirm Firefox version
    If the product is Firefox, check the version number shown in Help > About Firefox. Compare it to the affected range: versions 17.0 through 23.0.1, or any version below 24.0.
    Affected if Firefox version is 17.0, 17.0.1, 17.0.2, 19.0, 19.0.1, 19.0.2, 20.0, 20.0.1, 21.0, 22.0, 23.0, 23.0.1, or any version below 24.0
  3. Confirm Thunderbird version
    If the product is Thunderbird, check the version number shown in Help > About Thunderbird. Compare it to the affected range: versions 17.0 through 17.0.9, or any version below 24.0.
    Affected if Thunderbird version is 17.0 through 17.0.9, or any version below 24.0
  4. Confirm SeaMonkey version
    If the product is SeaMonkey, check the version number shown in Help > About SeaMonkey. Compare it to the affected range: versions 2.0 through 2.20, or any version below 2.21.
    Affected if SeaMonkey version is 2.0.x through 2.20, or any version below 2.21

You are affected if any installed Mozilla product (Firefox, Thunderbird, or SeaMonkey) matches the specific versions listed or falls below the fixed releases (Firefox 24.0, Thunderbird 24.0, SeaMonkey 2.21, or Firefox/Thunderbird ESR 17.0.9).

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

Upgrade to Firefox 24.0+, Thunderbird 24.0+, SeaMonkey 2.21+, or Firefox/Thunderbird ESR 17.0.9+. In enterprise environments, test and deploy patches through standard software distribution mechanisms.

Recommended fix High confidence

Firefox 24.0+, Firefox ESR 17.0.9+, Thunderbird 24.0+, Thunderbird ESR 17.0.9+, SeaMonkey 2.21+

  1. 1. Back up your current browser profile (bookmarks, passwords, extensions) to prevent data loss
  2. 2. For Windows: Open Firefox/Thunderbird, go to Help > About to check current version, then download the latest from https://www.mozilla.org/
  3. 3. For Linux: Use your package manager (e.g., 'sudo apt-get update && sudo apt-get upgrade firefox' or 'sudo yum update firefox')
  4. 4. For macOS: Use the built-in updater via Firefox/Thunderbird > About or download from https://www.mozilla.org/
  5. 5. After upgrade, verify the version in Help > About confirms 24.0+ for Firefox/Thunderbird or 2.21+ for SeaMonkey
  6. 6. Reinstall any disabled extensions that may have been incompatible with the old version
Caveat Minor: Some legacy browser extensions/add-ons may be incompatible with newer versions; review add-ons after upgrade

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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