dbcve.org
FirefoxWeb browser · Mozilla

CVE-2013-1701

HIGH · 10.0 CVSS v2.0 Published 2013-08-07
Fix available
A fix is available. Upgrade to after 22.0 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 23.0, Firefox ESR 17.x before 17.0.8, Thunderbird before 17.0.8, Thunderbird ESR 17.x before 17.0.8, and SeaMonkey before 2.20 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

Multiple memory corruption vulnerabilities in Mozilla's Gecko browser engine allow remote attackers to crash Firefox, Thunderbird, SeaMonkey or potentially execute arbitrary code via unknown vectors in the browser rendering engine.

MitigationApply vendor patches by updating to Firefox 23.0+, Firefox ESR 17.0.8+, Thunderbird 17.0.8+, Thunderbird ESR 17.0.8+, or SeaMonkey 2.20+ to remediate these critical browser engine flaws.

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<= 22.0= 19.0= 19.0.1= 19.0.2
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
ThunderbirdApplication
Affected:<= 17.0.7= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4= 17.0.5= 17.0.6
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

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
    Check for presence of Firefox, Thunderbird, or SeaMonkey on the system. On Windows, look in Program Files; on Linux, check /usr/bin or package manager; on macOS, check /Applications.
    Affected if Any of these three products are installed
  2. Check 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.x, 19.0, 19.0.1, 19.0.2, or 22.0 or lower (any version from 17.0 through 22.0)
  3. Check Thunderbird version
    In Thunderbird, go to Help > About Thunderbird, or run 'thunderbird --version' from command line.
    Affected if Version is 17.0.x or any version from 17.0 through 17.0.7 (including 17.0.8+ but the affected range shows <=17.0.7)
  4. Check SeaMonkey version
    In SeaMonkey, go to Help > About SeaMonkey, or run 'seamonkey --version' from command line.
    Affected if Version is 2.0.x (2.0 through 2.0.10) or 2.20 or lower

If the installed Firefox version is 17.0.x, 19.0-19.0.2, or 22.0 or lower; or Thunderbird is 17.0.x up to 17.0.7; or SeaMonkey is 2.0.x or 2.20 or lower, the environment is affected by this memory corruption flaw.

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

Apply vendor patches by updating to Firefox 23.0+, Firefox ESR 17.0.8+, Thunderbird 17.0.8+, Thunderbird ESR 17.0.8+, or SeaMonkey 2.20+ to remediate these critical browser engine flaws.

Recommended fix High confidence

Firefox 23.0+ | Firefox ESR 17.0.8+ | Thunderbird 17.0.8+ | Thunderbird ESR 17.0.8+ | SeaMonkey 2.20+

  1. 1. Identify the currently installed Mozilla product (Firefox, Firefox ESR, Thunderbird, Thunderbird ESR, or SeaMonkey) and its exact version
  2. 2. For Firefox 17.x users: upgrade to Firefox 23.0 or later
  3. 3. For Firefox ESR 17.x users: upgrade to Firefox ESR 17.0.8 or later
  4. 4. For Thunderbird users: upgrade to Thunderbird 17.0.8 or later
  5. 5. For Thunderbird ESR 17.x users: upgrade to Thunderbird ESR 17.0.8 or later
  6. 6. For SeaMonkey users: upgrade to SeaMonkey 2.20 or later
  7. 7. After upgrading, verify the new version by checking Help > About (or equivalent)
  8. 8. Ensure any third-party extensions/plugins are compatible with the new version
Caveat Major version upgrades (e.g., Firefox 17 to 23) 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,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 $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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