dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2015-4474

HIGH · 10.0 CVSS v2.0 Published 2015-08-16
Fix available
A fix is available. Upgrade to after 39.0.3 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 40.0 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 · moderate confidence

Multiple memory corruption vulnerabilities existed in the browser engine of Mozilla Firefox prior to version 40.0. These unspecified flaws could be exploited by remote attackers through unknown vectors to cause application crashes (denial of service) or potentially achieve arbitrary code execution.

MitigationUpgrade Mozilla Firefox to version 40.0 or later to remediate these 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 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
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 15.04
FirefoxWeb browser
Affected:<= 39.0.3
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
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. Check if Mozilla Firefox is installed
    Run: which firefox or dpkg -l | grep firefox or rpm -qa | grep firefox depending on your Linux distribution
    Affected if Firefox is not installed means the vulnerability does not apply to this system
  2. Determine installed Firefox version
    Run: firefox --version or about:firefox in the browser address bar
    Affected if Version is 39.0.3 or lower (any version <= 39.0.3)
  3. Compare version to affected range
    The affected range is any version prior to 40.0. If your version is 39.0.3 or lower, you are within the affected range. Versions 40.0 and later are not affected
    Affected if Installed version is less than 40.0 (e.g., 39.0.3, 39.0.2, 38.x, etc.)
  4. Verify OS version for context
    Run: lsb_release -a (Ubuntu) or cat /etc/os-release (general Linux) to confirm Ubuntu 12.04, 14.04, 15.04 or OpenSUSE 13.1/13.2
    Affected if Running Ubuntu 12.04/14.04/15.04 or OpenSUSE 13.1/13.2 with Firefox <=39.0.3 present

You are affected if Mozilla Firefox version 39.0.3 or any earlier version is installed on your system, regardless of operating system.

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

Upgrade Mozilla Firefox to version 40.0 or later to remediate these browser engine vulnerabilities.

Recommended fix High confidence

Firefox 40.0 or later (preferably latest stable release)

  1. Check current Firefox version by navigating to about:firefox or running 'firefox --version'
  2. Update your package manager: sudo apt-get update (Ubuntu) or sudo zypper refresh (openSUSE)
  3. Upgrade Firefox to version 40.0 or later: sudo apt-get upgrade firefox (Ubuntu) or sudo zypper update firefox (openSUSE)
  4. Alternatively, download and install Firefox 40.0 or later directly from mozilla.org
  5. Restart Firefox after upgrade to ensure the new version is active
  6. Verify the installed version is 40.0 or higher
Caveat Minimal risk; upgrading to a newer Firefox version may require adjustment to user preferences and extensions compatibility

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

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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