dbcve.org
FirefoxWeb browser · Mozilla

CVE-2014-1533

HIGH · 10.0 CVSS v2.0 Published 2014-06-11
Fix available
A fix is available. Upgrade to after 29.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 30.0, Firefox ESR 24.x before 24.6, and Thunderbird before 24.6 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 · high confidence

Multiple memory corruption vulnerabilities in the Mozilla browser engine allowed remote attackers to crash Firefox or Thunderbird applications, or potentially achieve arbitrary code execution, via unspecified vectors. These were critical flaws in the browser rendering engine affecting memory handling.

MitigationUpgrade immediately to Firefox 30.0 or later, Firefox ESR 24.6 or later, or Thunderbird 24.6 or later. This is a critical severity vulnerability with documented in-the-wild exploitation.

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:= 24.0= 24.0.1= 24.0.2= 24.1.0= 24.1.1<= 29.0.1
Firefox EsrWeb browser
Affected:= 24.2= 24.3= 24.4= 24.5

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 Firefox version
    Open Firefox, click Help > About Firefox (or navigate to about:support). The version number is displayed in the window title or on the page.
    Affected if The version matches 24.0, 24.0.1, 24.0.2, 24.1.0, 24.1.1, or any version from 24.2 through 29.0.1
  2. Identify Firefox ESR version
    Open Firefox ESR, click Help > About Firefox ESR. ESR versions display in the format 24.x.
    Affected if The version is 24.2, 24.3, 24.4, or 24.5
  3. Identify Thunderbird version
    Open Thunderbird, click Help > About Thunderbird. Thunderbird shares the Gecko engine with Firefox and is affected by the same memory corruption flaws.
    Affected if The installed Thunderbird version corresponds to the affected Firefox timeline (versions containing Gecko engine versions matching Firefox 24.0 through 29.0.1)

A user is affected if Firefox (any channel) version is 24.0 through 29.0.1, Firefox ESR is 24.2 through 24.5, or Thunderbird uses an equivalently affected Gecko engine version.

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 29.0.1
Interim mitigation

Upgrade immediately to Firefox 30.0 or later, Firefox ESR 24.6 or later, or Thunderbird 24.6 or later. This is a critical severity vulnerability with documented in-the-wild exploitation.

Recommended fix High confidence

Firefox 30.0 or Firefox ESR 24.6 or later

  1. 1. Back up any important browser data (bookmarks, passwords, extensions)
  2. 2. Close all instances of Firefox
  3. 3. Download Firefox 30.0 or later from the official Mozilla website (https://www.mozilla.org/firefox/)
  4. 4. For Firefox ESR users, download Firefox ESR 24.6 or later from the Mozilla website
  5. 5. Run the installer and follow the prompts to upgrade
  6. 6. After installation, verify the version by navigating to Help > About Firefox
  7. 7. Confirm the installed version shows 30.0 or higher (or ESR 24.6 or higher for ESR users)

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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