dbcve.org
FirefoxWeb browser · Mozilla

CVE-2014-1519

HIGH · 9.3 CVSS v2.0 Published 2014-04-30
Fix available
A fix is available. Upgrade to 2.26 / 29.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 29.0 and SeaMonkey before 2.26 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

A detailed technical summary for this CVE is being prepared.

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:< 29.0
Ubuntu LinuxOperating system
Affected:= 12.04= 12.10= 13.10= 14.04
FedoraOperating system
Affected:= 19= 20
SeamonkeyApplication
Affected:< 2.26
OpensuseOperating system
Affected:= 12.3= 13.1

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 2.26 / 29.0 or later
Fixed in 2.2629.0
Vendor patch bugzilla.mozilla.org →
Recommended fix High confidence

Firefox 29.0 or later; SeaMonkey 2.26 or later

  1. For Firefox users: Upgrade to Firefox 29.0 or later via the Mozilla website or system package manager (e.g., 'apt-get update && apt-get install firefox' on Ubuntu, 'yum update firefox' on Fedora)
  2. For SeaMonkey users: Upgrade to SeaMonkey 2.26 or later from the Mozilla SeaMonkey website
  3. For Linux distributions (Ubuntu 12.04/12.10/13.10/14.04, Fedora 19/20, OpenSUSE 12.3/13.1): Run system update to receive the patched Firefox package (e.g., 'apt-get update && apt-get upgrade' or 'yum update' or 'zypper update')
  4. Restart the browser after upgrading to ensure the patched version is loaded
  5. Verify the installed version matches or exceeds the fixed release (Firefox >= 29.0, SeaMonkey >= 2.26)
Caveat Firefox 29.0 introduced the Australis UI redesign which changed the visual appearance and some user interface elements

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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