CVE-2017-3040
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 · uneditedAdobe Acrobat Reader versions 11.0.19 and earlier, 15.006.30280 and earlier, 15.023.20070 and earlier have an exploitable memory corruption vulnerability in the JBIG2 image compression module. Successful exploitation could lead to arbitrary code execution.
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 memory corruption vulnerability exists in the JBIG2 image compression module of Adobe Acrobat Reader. The flaw allows attackers to trigger arbitrary code execution via specially crafted PDF files containing malicious JBIG2 image data.
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<= 11.0.19<= 15.006.30280<= 15.023.20070<= 15.006.30280<= 15.023.20070<= 11.0.19CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/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.
-
Identify installed Adobe productOpen Adobe Acrobat or Reader, go to Help > About Adobe [Product Name] to see the exact product and version installedAffected if Any of the following products are present: Adobe Acrobat <= 11.0.19, Adobe Acrobat Dc <= 15.006.30280 or <= 15.023.20070, Adobe Acrobat Reader Dc <= 15.006.30280 or <= 15.023.20070, Adobe Reader <= 11.0.19
-
Confirm exact version numberLocate the version displayed in the About dialog (for example, 11.0.19, 15.006.30280, or 15.023.20070)Affected if Version number is 11.0.19 or lower for classic products, or 15.006.30280 / 15.023.20070 or lower for DC variants
-
Verify JBIG2 module is presentCheck for the JBIG2Filter.dll or related JBIG2 processing DLLs in the Adobe program installation directory (typically in Program Files/Adobe)Affected if The JBIG2 filter DLL exists in the installation directory and the application can process PDF files containing JBIG2 compressed images
-
Check if PDF handling is enabledOpen Adobe preferences and verify that PDF rendering and image filters are enabled under the Categories > Security (Enhanced) or Plugins settingsAffected if PDF files can be opened and rendered, which means the JBIG2 module is active and vulnerable to maliciously crafted files
You are affected if any Adobe Acrobat, Acrobat Reader, or Reader DC version is 11.0.19 or lower, or DC versions 15.006.30280/15.023.20070 or lower, and the application can open PDF files with JBIG2 images.
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.
From vendor dataUpdate Adobe Acrobat Reader to a version newer than 11.0.19, 15.006.30280, or 15.023.20070 respectively to patch the JBIG2 memory corruption vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3040 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-3040 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