CVE-2013-1732
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 · uneditedBuffer overflow in the nsFloatManager::GetFlowArea function 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 allows remote attackers to execute arbitrary code via crafted use of lists and floats within a multi-column layout.
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 confidenceBuffer overflow in Mozilla's nsFloatManager::GetFlowArea function when handling crafted lists and floats within multi-column layouts, allowing remote arbitrary code execution.
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<= 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<= 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= 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<= 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.8CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 the Mozilla product installedCheck which Mozilla application is installed: Firefox, SeaMonkey, or Thunderbird. On Windows check Programs and Features or the application executable properties. On Linux check the package manager or look for application binaries in /usr/bin or /opt.Affected if Any of Firefox, SeaMonkey, or Thunderbird is installed
-
Determine the installed Firefox versionFor Firefox: Click menu > Help > About Firefox, or run 'firefox --version' from command line, or check the version in the executable properties.Affected if Version is 23.0.1 or lower, or any of 17.0 through 17.0.2, 19.0 through 20.0.1, 21.0, 22.0, or 23.0
-
Determine the installed SeaMonkey versionFor SeaMonkey: Click menu > Help > About SeaMonkey, or run 'seamonkey --version' from command line.Affected if Version is 2.20 or lower, or any of 2.0 through 2.0.10
-
Determine the installed Thunderbird versionFor Thunderbird: Click menu > Help > About Thunderbird, or run 'thunderbird --version' from command line. Identify if it is ESR or standard version.Affected if Standard version is 17.0.9 or lower, or any of 17.0 through 17.0.8. ESR version is any of 17.0 through 17.0.8.
-
Check for multi-column layout usageInspect web content or email content being rendered. Look for CSS 'column-count', 'column-width', or 'columns' properties in any HTML/CSS being processed, or check if the browser is visiting pages that use multi-column layouts.Affected if Multi-column CSS layouts are being rendered - this is the feature that must be enabled for the vulnerability to be triggerable
The user is affected if they have Firefox 23.0.1 or lower, SeaMonkey 2.20 or lower, or Thunderbird 17.0.9 or lower (or Thunderbird ESR 17.0.8 or lower) AND are processing multi-column layout content.
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 · scopedUpdate affected products to patched versions: Firefox 24.0+, Firefox ESR 17.0.9+, Thunderbird 24.0+, Thunderbird ESR 17.0.9+, or SeaMonkey 2.21+.
Firefox 24.0+; Firefox ESR 17.0.9+; Thunderbird 24.0+; Thunderbird ESR 17.0.9+; SeaMonkey 2.21+
- Check the current version of the installed Mozilla product (Firefox, SeaMonkey, Thunderbird, or Thunderbird ESR)
- For Firefox: upgrade to version 24.0 or later
- For Firefox ESR: upgrade to version 17.0.9 or later
- For Thunderbird: upgrade to version 24.0 or later
- For Thunderbird ESR: upgrade to version 17.0.9 or later
- For SeaMonkey: upgrade to version 2.21 or later
- After upgrading, restart the application to apply the changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1732 — 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 sources- www.mozilla.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- rhn.redhat.com
- www.debian.org
- www.securityfocus.com
- www.ubuntu.com
- www.ubuntu.com
- bugzilla.mozilla.org
- oval.cisecurity.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-1732 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