dbcve.org
FirefoxWeb browser · Mozilla

CVE-2013-1719

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, Thunderbird before 24.0, 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 · moderate confidence

Multiple memory corruption vulnerabilities in the Gecko layout engine in Firefox, Thunderbird, and SeaMonkey prior to version 24.0 allow remote attackers to cause denial of service via application crash or potentially execute arbitrary code through unspecified vectors.

MitigationUpgrade affected installations to Firefox 24.0, Thunderbird 24.0, SeaMonkey 2.21 or later to patch the browser engine vulnerabilities.

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
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 installed Mozilla product
    Check for Firefox, Thunderbird, or SeaMonkey installation by looking for the application in /Applications (macOS), Program Files (Windows), or /usr/bin (Linux). On Windows, check Add/Remove Programs or the application's executable properties.
    Affected if Any of the three products (Firefox, Thunderbird, or SeaMonkey) is installed
  2. Determine Firefox version
    In Firefox, type 'about:support' in the address bar and look for 'Version' under 'Application Basics'. Alternatively, use command line: 'firefox --version' on Linux, or right-click firefox.exe and select Properties on Windows.
    Affected if Version is 23.0.1 or lower, OR equals 19.0, 19.0.1, 19.0.2, 20.0, 20.0.1, 21.0, 22.0, or 23.0
  3. Determine Thunderbird version
    In Thunderbird, go to Help > About Thunderbird and look for the version number. Alternatively, use command line: 'thunderbird --version' on Linux, or check the executable properties on Windows.
    Affected if Version is 17.0.9 or lower, OR equals 17.0, 17.0.1, 17.0.2, 17.0.3, 17.0.4, 17.0.5, 17.0.6, 17.0.7, or 17.0.8
  4. Determine SeaMonkey version
    In SeaMonkey, go to Help > About SeaMonkey and look for the version number. Alternatively, use command line: 'seamonkey --version' on Linux, or check the executable properties on Windows.
    Affected if Version is 2.20 or lower, OR equals 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, or 2.0.10

You are affected if Firefox version is 23.0.1 or below (or specific 19.x-23.x versions), Thunderbird version is 17.0.9 or below (or specific 17.x versions), or SeaMonkey version is 2.20 or below (or specific 2.0.x 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 23.0.1
Interim mitigation

Upgrade affected installations to Firefox 24.0, Thunderbird 24.0, SeaMonkey 2.21 or later to patch the browser engine vulnerabilities.

Recommended fix High confidence

Firefox 24.0+, Thunderbird 24.0+, or SeaMonkey 2.21+

  1. Identify which Mozilla product is affected (Firefox, Thunderbird, or SeaMonkey)
  2. For Firefox: Navigate to the official Mozilla Firefox download page or use the built-in update mechanism (Help > About Firefox > Check for Updates)
  3. For Thunderbird: Navigate to the official Mozilla Thunderbird download page or use the built-in update mechanism (Help > About Thunderbird > Check for Updates)
  4. For SeaMonkey: Navigate to the official SeaMonkey download page
  5. Download and install Firefox 24.0 or later, Thunderbird 24.0 or later, or SeaMonkey 2.21 or later
  6. Restart the application after the update completes
  7. Verify the installed version by checking About Firefox/Thunderbird/SeaMonkey to confirm the update was successful
Caveat Upgrading to a new major version may cause compatibility issues with older browser extensions or add-ons; test critical workflows after upgrading

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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