dbcve.org
FirefoxWeb browser · Mozilla

CVE-2016-1953

HIGH · 8.8 CVSS v3.0 Published 2016-03-13
Fix available
A fix is available. Upgrade to after 44.0.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 45.0 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via vectors related to js/src/jit/arm/Assembler-arm.cpp, and unknown other 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

Memory corruption vulnerability in Mozilla Firefox's browser engine, specifically in the JavaScript JIT compiler's ARM assembler (js/src/jit/arm/Assembler-arm.cpp). The flaw allows remote attackers to cause denial of service through memory corruption and application crashes, or potentially execute arbitrary code via crafted web content.

MitigationUpgrade Mozilla Firefox to version 45.0 or later to apply the vendor patch addressing this vulnerability.

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:<= 44.0.2= 38.0= 38.0.1= 38.0.5= 38.1.0= 38.1.1= 38.2.0= 38.2.1= 38.3.0= 38.4.0= 38.5.0= 38.5.1
ThunderbirdApplication
Affected:<= 38.6.0
Suse Package Hub For Suse Linux EnterpriseApplication
Affected:= 12
LeapOperating system
Affected:= 42.1
OpensuseOperating system
Affected:= 13.1= 13.2

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
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installed Mozilla product
    Run command to determine if Firefox or Thunderbird is installed (e.g., which firefox, which thunderbird, or check installed packages)
    Affected if Neither Firefox nor Thunderbird is installed (not affected)
  2. Determine Firefox version
    Run 'firefox --version' or check Help > About Firefox to obtain the exact version number
    Affected if Version is 44.0.2 or lower, or matches any of: 38.0, 38.0.1, 38.0.5, 38.1.0, 38.1.1, 38.2.0, 38.2.1, 38.3.0, 38.4.0, 38.5.0, 38.5.1
  3. Determine Thunderbird version
    Run 'thunderbird --version' or check Help > About Thunderbird to obtain the exact version number
    Affected if Version is 38.6.0 or lower
  4. Verify system architecture
    Run 'uname -m' or 'arch' command to check if running on ARM architecture (armv7l, aarch64, etc.)
    Affected if System is running on ARM architecture and the installed Firefox/Thunderbird version is in the affected range (JIT compiler for ARM is the vulnerable component)
  5. Confirm JavaScript JIT is enabled
    In Firefox address bar, type 'about:config' and search for 'jit' or check that javascript.options.jit.content is not set to false
    Affected if JIT compilation is explicitly disabled (vulnerability does not apply as the vulnerable ARM assembler code is not executed)

User is affected if Firefox version 44.0.2 or lower, or any 38.x version, or Thunderbird version 38.6.0 or lower is installed AND the system runs on ARM architecture with JavaScript JIT enabled (default).

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.

From vendor data
Upgrade available Upgrade to a release after 44.0.2
Interim mitigation

Upgrade Mozilla Firefox to version 45.0 or later to apply the vendor patch addressing this vulnerability.

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-2016-1953 — 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-2016-1953 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