CVE-2014-1576
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 · uneditedHeap-based buffer overflow in the nsTransformedTextRun function in Mozilla Firefox before 33.0, Firefox ESR 31.x before 31.2, and Thunderbird 31.x before 31.2 allows remote attackers to execute arbitrary code via Cascading Style Sheets (CSS) token sequences that trigger changes to capitalization style.
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 confidenceHeap-based buffer overflow in Mozilla Firefox and Thunderbird's nsTransformedTextRun function when processing CSS token sequences that modify text capitalization (e.g., text-transform: uppercase). The vulnerability allows remote attackers to execute arbitrary code via specially crafted web pages or emails containing malicious CSS.
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= 31.0= 31.1.0<= 32.0= 30.0= 31.0= 31.1.0CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 if Mozilla Firefox is installedCheck for Firefox installation: On Windows, look in Program Files for Firefox folder, or check registry HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Mozilla Firefox. On Linux, run 'which firefox' or check package manager. On Mac, check /Applications/Firefox.app.Affected if Firefox is installed and version is 30.0, 31.0, 31.1.0, or 32.0 or lower
-
Identify if Mozilla Thunderbird is installedCheck for Thunderbird installation: On Windows, look in Program Files for Thunderbird folder. On Linux, run 'which thunderbird' or check package manager. On Mac, check /Applications/Thunderbird.app.Affected if Thunderbird is installed and version is 31.0 or 31.1.0
-
Confirm exact Firefox versionIn Firefox, navigate to Help > About Firefox, or run 'firefox --version' from command line, or check the version file in the Firefox installation directory.Affected if Version equals 30.0, 31.0, 31.1.0, or is 32.0 or lower (for example 32.0, 31.2, 31.1, 31.0.1, 30.1, 30.0.1)
-
Confirm exact Thunderbird versionIn Thunderbird, navigate to Help > About Thunderbird, or run 'thunderbird --version' from command line.Affected if Version equals 31.0 or 31.1.0
A user is affected if they have Firefox version 30.0, 31.0, 31.1.0, or 32.0 or lower, or Thunderbird version 31.0 or 31.1.0 installed on their system.
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.
From vendor dataUpdate affected products to Firefox 33.0, Firefox ESR 31.2, Thunderbird 31.2 or later. Avoid browsing untrusted websites or opening suspicious email content until patches are applied.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1576 — 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.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- www.debian.org
- www.debian.org
- www.oracle.com
- www.securityfocus.com
- www.securitytracker.com
- www.securitytracker.com
- www.ubuntu.com
- www.ubuntu.com
- advisories.mageia.org
- bugzilla.mozilla.org
- security.gentoo.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-1576 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