CVE-2015-4495
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 · uneditedThe PDF reader in Mozilla Firefox before 39.0.3, Firefox ESR 38.x before 38.1.1, and Firefox OS before 2.2 allows remote attackers to bypass the Same Origin Policy, and read arbitrary files or gain privileges, via vectors involving crafted JavaScript code and a native setter, as exploited in the wild in August 2015.
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 confidenceA Same Origin Policy bypass vulnerability in Mozilla Firefox's PDF reader allows remote attackers to read arbitrary files or gain privileges via crafted JavaScript code exploiting a native setter. The vulnerability was actively exploited in the wild in August 2015.
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< 39.0.3>= 38.0, < 38.1.1< 2.2= 12.04= 14.04= 15.04= 5.0= 6.0= 7.0= 6.7= 7.1= 7.2= 7.3= 7.4= 7.5= 7.6= 7.7= 5.0= 6.0= 7.0= 7.3= 7.4= 7.6= 7.7= 7.3= 7.6= 7.7CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Check Firefox browser versionOpen Firefox and navigate to Help > About Firefox, or run 'firefox --version' from command line. Also check 'about:support' in the address bar for detailed version info.Affected if Version is < 39.0.3, or is >= 38.0 but < 38.1.1 (ESR versions)
-
Confirm PDF reader component is in useNavigate to about:preferences#general in Firefox and locate the 'PDF Documents' section. Check if 'Preview in Firefox' is selected (the built-in PDF.js reader).Affected if The built-in PDF viewer (PDF.js) is enabled; the vulnerability exists in this component
-
Check Firefox OS version on mobile devicesOn Firefox OS devices, go to Settings > About Phone > Software Update or check the device documentation for the Firefox OS version.Affected if Firefox OS version is < 2.2
-
Verify Linux distribution package versionsOn Ubuntu systems run 'dpkg -l | grep firefox' or 'apt-cache policy firefox'. On RHEL systems run 'rpm -qa | grep firefox' or 'yum info firefox'.Affected if The packaged Firefox version matches the affected version ranges for the respective distribution
You are affected if you run any Firefox version before 39.0.3 (or ESR before 38.1.1) or Firefox OS before 2.2, and have the built-in PDF viewer enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.238.1.139.0.3
Update Firefox to version 39.0.3 or later, Firefox ESR to 38.1.1 or later, or Firefox OS to 2.2 or later to patch the vulnerability.
Firefox 39.0.3 (or later) / Firefox ESR 38.1.1 (or later) / Firefox OS 2.2 (or later)
- Upgrade Firefox to version 39.0.3 or later for the release channel
- If using Firefox ESR, upgrade to version 38.1.1 or later
- For Firefox OS devices, upgrade to version 2.2 or later
- On Linux systems (Ubuntu 12.04, 14.04, 15.04 or Enterprise Linux variants), apply the vendor security update through your system package manager (e.g., apt-get update && apt-get upgrade firefox, or yum update firefox)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4495 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- www.oracle.com
- www.exploit-db.com
- www.mozilla.org
- blog.mozilla.org
- www.oracle.com
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- www.securityfocus.com
- www.securitytracker.com
- www.ubuntu.com
- security.gentoo.org
- www.exploit-db.com
- bugzilla.mozilla.org
- bugzilla.mozilla.org
- www.cisa.gov
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-4495 in production — separate from our analysis above.
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.
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.
- 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