FirefoxWeb browser · Mozilla

CVE-2016-1930

CRITICAL · 9.8 CVSS v3.0 Published 2016-01-31

Fix available

A fix is available. Upgrade to after 43.0.4 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 44.0 and Firefox ESR 38.x before 38.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

dbcve analysis · high confidence

Multiple memory corruption vulnerabilities in Mozilla Firefox's browser engine allow remote attackers to cause denial of service through application crashes or potentially achieve arbitrary code execution via unknown attack vectors.

MitigationUpgrade Mozilla Firefox to version 44.0 or later, and Firefox ESR to version 38.6 or later, to patch the browser engine vulnerabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

FirefoxWeb browser

Affected:<= 43.0.4= 38.0= 38.1.0= 38.2.0= 38.3.0= 38.4.0= 38.5.0

LinuxOperating system

Affected:= 5.0= 6= 7

LeapOperating system

Affected:= 42.1

OpensuseOperating system

Affected:= 13.1= 13.2

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check installed Firefox version

Open Firefox, go to Help > About Firefox, or run 'firefox --version' in terminal

Affected if Version is 43.0.4 or lower, or specifically 38.0, 38.1.0, 38.2.0, 38.3.0, 38.4.0, or 38.5.0
Check Firefox package version on Oracle Linux

Run 'rpm -q firefox' to query the installed Mozilla Firefox package version

Affected if Package version corresponds to Firefox 43.0.4 or lower, or any 38.x version (38.0 through 38.5.0)
Check Firefox package version on openSUSE Leap

Run 'rpm -q firefox' or 'zypper se firefox' to query the installed Mozilla Firefox package version

Affected if Package version corresponds to Firefox 43.0.4 or lower, or any 38.x version, including versions shipped with openSUSE Leap 42.1
Check Firefox package version on openSUSE

Run 'rpm -q firefox' or 'zypper se firefox' to query the installed Mozilla Firefox package version

Affected if Package version corresponds to Firefox 43.0.4 or lower, or any 38.x version, including versions shipped with openSUSE 13.1 or 13.2

You are affected if your installed Firefox version is 43.0.4 or any version from 38.0 through 38.5.0, regardless of whether it was installed directly or via your Linux distribution's package manager.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 43.0.4

Interim mitigation

Upgrade Mozilla Firefox to version 44.0 or later, and Firefox ESR to version 38.6 or later, to patch the browser engine vulnerabilities.

Recommended fix High confidence

Firefox 44.0 or Firefox ESR 38.6

Back up any critical browser data (bookmarks, passwords, saved forms)
Close all instances of Firefox
Upgrade Firefox to version 44.0 or later, or Firefox ESR to version 38.6 or later
On Linux systems, use the system's package manager (e.g., zypper for OpenSUSE, yum/dnf for RHEL-based) to update the firefox package: 'sudo zypper update firefox' or 'sudo yum update firefox'
Verify the installed version matches or exceeds the fixed release: 'firefox --version'
Restart Firefox and test critical functionality

Caveat Minor - some legacy browser extensions or add-ons may be incompatible with the newer major version

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

Fix this in Firefox Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

7.0 hours of engineering $1,240

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,984.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1930 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2016-1930?

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.

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

At a glance

A fix existsUpgrade to after 43.0.4 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 6.0%

Affects: Firefox

Remediation

A high-priority fix

Fix this in Firefox 7 hrs · Low

Typical engagement from $1,240

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2016-1930 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References