CVE-2017-3051
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 image conversion engine, related to parsing of JPEG files. 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 confidenceAdobe Acrobat Reader contains a memory corruption vulnerability in its image conversion engine when parsing specially crafted JPEG files. The vulnerability allows an attacker to achieve arbitrary code execution via a malicious JPEG file that triggers heap corruption during the parsing process.
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, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). Note the exact product name and version number displayed.Affected if The product is Adobe Acrobat, Adobe Acrobat Dc, Adobe Acrobat Reader Dc, or Adobe Reader.
-
Determine the product variantCheck whether you have the 'Classic' version or 'Dc' variant. In the About dialog, look for 'Dc' in the product name. The Dc versions have two separate affected version branches (15.006.30280 and 15.023.20070).Affected if The product is Adobe Acrobat Dc or Adobe Acrobat Reader Dc.
-
Compare version against affected rangesMatch your installed version number against these affected ranges: Adobe Acrobat/Reader classic <= 11.0.19; Dc versions <= 15.006.30280 or <= 15.023.20070. If your version falls within any of these ranges, you are affected.Affected if The installed version is less than or equal to 11.0.19 for classic versions, or less than or equal to 15.006.30280 or 15.023.20070 for Dc versions.
-
Verify image conversion capability is presentConfirm the image conversion engine is available. In Adobe Reader/Acrobat, try opening a JPEG file via File > Open, or use the Convert to PDF feature (File > Create PDF > From File) to ensure the JPEG parsing functionality is present.Affected if The image conversion engine is enabled and can parse JPEG files.
You are affected if Adobe Acrobat or Reader is installed with a version falling within the affected ranges (11.0.19 or below for classic, 15.006.30280 or 15.023.20070 or below for Dc) and the application can parse JPEG files.
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 dataApply the vendor-supplied patch by updating Adobe Acrobat Reader to a version later than 11.0.19, 15.006.30280, or 15.023.20070 respectively. Organizations should prioritize patching given the high CVSS score and code execution potential.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3051 — 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-3051 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