CVE-2013-1680
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 · uneditedUse-after-free vulnerability in the nsFrameList::FirstChild function in Mozilla Firefox before 21.0, Firefox ESR 17.x before 17.0.6, Thunderbird before 17.0.6, and Thunderbird ESR 17.x before 17.0.6 allows remote attackers to execute arbitrary code or cause a denial of service (heap memory corruption) via unspecified 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 confidenceUse-after-free vulnerability in Mozilla Firefox and Thunderbird's nsFrameList::FirstChild function allows remote attackers to execute arbitrary code via heap memory corruption. The vulnerability exists in unspecified vectors within the browser rendering engine.
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<= 20.0.1= 19.0= 19.0.1= 19.0.2= 20.0= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4= 17.0.5<= 17.0.5= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4= 17.0.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mozilla productCheck if Firefox or Thunderbird is installed. On Windows, look in Program Files. On macOS, check /Applications. On Linux, check for firefox or thunderbird packages.Affected if Either Firefox or Thunderbird is installed
-
Check Firefox version numberOpen Firefox, click Help > About Firefox, or navigate to about:support in the address bar. Note the version number shown (e.g., 20.0.1, 19.0.2, 17.0.5).Affected if Version is 20.0.1 or lower, or is 19.0, 19.0.1, 19.0.2, 20.0, or any 17.0.x version through 17.0.5
-
Check Thunderbird version numberOpen Thunderbird, click Help > About Thunderbird, or navigate to about:support in the address bar. Note the version number shown (e.g., 17.0.4, 17.0.5).Affected if Version is 17.0.5 or lower, including any 17.0, 17.0.1, 17.0.2, 17.0.3, or 17.0.4 (both standard and ESR editions)
-
Confirm no specific feature workaround existsThis vulnerability is in the core rendering engine (nsFrameList::FirstChild function) and is triggered by malformed content processed by the browser. There is no configuration toggle or setting that prevents it - the issue exists in the affected versions regardless of user settings.Affected if Running an affected version means the vulnerability is present; no browser settings can mitigate it
A user is affected if they are running Firefox 20.0.1 or lower, any Firefox 17.0.x version, or Thunderbird 17.0.5 or lower (including Thunderbird ESR 17.0.x).
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Firefox 21.0 or later, Firefox ESR 17.0.6 or later, Thunderbird 17.0.6 or later, or Thunderbird ESR 17.0.6 or later.
Firefox 21.0+, Firefox ESR 17.0.6+, Thunderbird 17.0.6+, or Thunderbird ESR 17.0.6+
- Check the current installed version of Firefox or Thunderbird by opening the application and navigating to Help > About (or the equivalent menu)
- Identify which product and version is installed (Firefox, Firefox ESR, Thunderbird, or Thunderbird ESR)
- For Firefox users: Download and install Firefox 21.0 or later from the official Mozilla website (mozilla.org/firefox)
- For Firefox ESR users: Download and install Firefox ESR 17.0.6 or later from Mozilla's ESR download page
- For Thunderbird users: Download and install Thunderbird 17.0.6 or later from the official Mozilla website (mozilla.org/thunderbird)
- For Thunderbird ESR users: Download and install Thunderbird ESR 17.0.6 or later from Mozilla's ESR download page
- Close and fully restart the application after installation
- Verify the installed version by checking Help > About to confirm the version number matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1680 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-1680 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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