dbcve.org
FirefoxWeb browser · Mozilla

CVE-2013-1710

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
The crypto.generateCRMFRequest function 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 allows remote attackers to execute arbitrary JavaScript code or conduct cross-site scripting (XSS) attacks via vectors related to Certificate Request Message Format (CRMF) request generation.

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 crypto.generateCRMFRequest function in Mozilla Firefox, Thunderbird, and SeaMonkey fails to properly sanitize input during Certificate Request Message Format (CRMF) request generation, allowing remote attackers to inject and execute arbitrary JavaScript code or conduct cross-site scripting (XSS) attacks.

MitigationUpdate all affected Mozilla products to version 23.0 or higher for Firefox, 17.0.8 or higher for ESR versions, and 2.20 or higher for SeaMonkey to remediate this vulnerability.

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:<= 22.0= 19.0= 19.0.1= 19.0.2= 20.0= 20.0.1= 21.0= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4
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
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
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

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 check its name. In Windows, this can also be done via Programs and Features or by locating the executable. Common install paths: Firefox (C:\Program Files\Mozilla Firefox\firefox.exe), Thunderbird (C:\Program Files\Mozilla Thunderbird\thunderbird.exe), SeaMonkey (C:\Program Files\SeaMonkey\seamonkey.exe)
    Affected if The product is Mozilla Firefox, Thunderbird, or SeaMonkey
  2. Determine the installed version
    For Firefox: type 'about:config' in the address bar or go to Help > About Firefox. For Thunderbird: go to Help > About Thunderbird. For SeaMonkey: go to Help > About SeaMonkey. Alternatively, check the application.ini or version.ini file in the application installation directory
    Affected if The exact version cannot be determined from the product
  3. Compare Firefox version against affected ranges
    If Firefox is installed, note the version number. Affected versions are: 17.0, 17.0.1, 17.0.2, 17.0.3, 17.0.4, 19.0, 19.0.1, 19.0.2, 20.0, 20.0.1, 21.0, 22.0, or any version lower than 17.0
    Affected if Firefox version is 17.0.x, 19.0.x, 20.0.x, 21.0.x, 22.0, or below 17.0
  4. Compare Thunderbird version against affected ranges
    If Thunderbird is installed, note the version number. Affected versions are: 17.0 through 17.0.7 inclusive, or any version below 17.0
    Affected if Thunderbird version is 17.0.x (including ESR variants) or any version below 17.0
  5. Compare SeaMonkey version against affected ranges
    If SeaMonkey is installed, note the version number. Affected versions are: 2.0 through 2.0.10 inclusive, 2.20, or any version below 2.0
    Affected if SeaMonkey version is 2.0.x or 2.20 or any version below 2.0

The environment is affected if any of Firefox (versions 17.0-17.0.4, 19.0-19.0.2, 20.0-20.0.1, 21.0, 22.0 or below 17.0), Thunderbird (versions 17.0-17.0.7 or below 17.0), or SeaMonkey (versions 2.0-2.0.10, 2.20 or below 2.0) is installed.

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

Update all affected Mozilla products to version 23.0 or higher for Firefox, 17.0.8 or higher for ESR versions, and 2.20 or higher for SeaMonkey to remediate this vulnerability.

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. Check current installed version of Firefox, SeaMonkey, Thunderbird, or Thunderbird ESR
  2. For Firefox: Upgrade to version 23.0 or later
  3. For Firefox ESR: Upgrade to version 17.0.8 or later
  4. For Thunderbird: Upgrade to version 17.0.8 or later
  5. For Thunderbird ESR: Upgrade to version 17.0.8 or later
  6. For SeaMonkey: Upgrade to version 2.20 or later
  7. Restart the application after upgrade
  8. Verify the upgrade was successful by checking the new version number

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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