CVE-2017-3052
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 a memory address leak vulnerability in the image conversion engine, related to parsing of EMF - enhanced meta file format.
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 confidenceMemory address leak vulnerability in Adobe Acrobat Reader's image conversion engine when parsing EMF (Enhanced Metafile) files. The vulnerability exposes memory addresses during image conversion, which could aid an attacker in bypassing security mitigations like ASLR.
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
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 the installed Adobe productCheck Programs and Features or use command 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1033-7B44-AC0F074E4100}" /v DisplayName' for Reader or similar registry paths for Acrobat productsAffected if The installed product is Adobe Acrobat, Adobe Acrobat Reader, Adobe Acrobat DC, or Adobe Acrobat Reader DC
-
Determine the exact version of Adobe Acrobat or ReaderRight-click on the application in Help > About Adobe Acrobat/Reader, or use 'reg query' to read the Version key from the uninstall registry entryAffected if The displayed version number is at or below the affected thresholds for your product variant
-
Compare installed version against affected rangesMatch your product type and version to: Acrobat <= 11.0.19; Acrobat DC Classic <= 15.006.30280; Acrobat DC Continuous <= 15.023.20070; Reader DC Classic <= 15.006.30280; Reader DC Continuous <= 15.023.20070; Reader <= 11.0.19Affected if Your version falls at or below any of these thresholds for the matching product variant
-
Verify the image conversion component is presentThe EMF parsing occurs in the image conversion engine which is a core component of Acrobat/Reader; confirm the application has full functionality rather than a minimal installationAffected if The full Adobe Acrobat or Reader application is installed with standard image conversion capabilities
You are affected if you have Adobe Acrobat or Reader installed with a version at or below the affected thresholds for your specific product variant, and the application processes EMF files through its image conversion feature.
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 later than 11.0.19, 15.006.30280, or 15.023.20070 to receive the security patch for this vulnerability.
- 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-2017-3052 — 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-3052 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