AcrobatApplication · Adobe

CVE-2017-3018

HIGH · 7.8 CVSS v3.0 Published 2017-04-12
Fix available
A fix is available. Upgrade to after 15.023.20070 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Adobe 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 renderer functionality. 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 · moderate confidence

Adobe Acrobat Reader contains a memory corruption vulnerability in its PDF rendering functionality. The flaw allows attackers to trigger memory corruption through specially crafted PDF documents, potentially enabling arbitrary code execution on affected systems.

MitigationUpdate Adobe Acrobat Reader to the latest version to patch the memory corruption vulnerability in the renderer component.

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
AcrobatApplication
Affected:<= 11.0.19
Acrobat DcApplication
Affected:<= 15.006.30280<= 15.023.20070
Acrobat Reader DcApplication
Affected:<= 15.006.30280<= 15.023.20070
ReaderApplication
Affected:<= 11.0.19

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Adobe Acrobat or Reader is installed
    Check for the presence of Adobe Acrobat or Adobe Reader on the system. Common install paths: C:\Program Files\Adobe\Adobe Acrobat <version>\ or C:\Program Files (x86)\Adobe\Reader <version>\. On macOS, check /Applications for Adobe Acrobat or Adobe Reader apps.
    Affected if Adobe Acrobat or Adobe Reader is not installed, the system is not affected by this specific CVE.
  2. Identify the exact installed version
    Right-click the Adobe application in Programs and Features, or open the application and go to Help > About Adobe Acrobat/Reader to display the exact version number.
    Affected if The installed version number matches or falls below the affected ranges (11.0.19 or earlier for classic versions, 15.006.30280 or 15.023.20070 or earlier for DC versions).
  3. Confirm the PDF rendering component is in use
    The vulnerability exists in the PDF rendering functionality. This component is enabled by default in all standard installations. No additional configuration check is needed unless a restricted environment disables PDF rendering entirely.
    Affected if PDF rendering is enabled (default state), making the version vulnerable if it falls within the affected ranges.
  4. Check for security patch indicators
    Look for installed Adobe security updates. In Windows, check Programs and Features for installed updates containing dates from June 2017 or later, or examine the application's version number which would be higher than the affected ranges after patching.
    Affected if No post-June-2017 security patches are installed and the version remains at or below the affected thresholds.

A system is affected if Adobe Acrobat or Adobe Reader is installed with a version at or below 11.0.19 (classic) or at or below 15.006.30280 / 15.023.20070 (DC), and PDF rendering functionality is enabled (default).

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.

From vendor data
Upgrade available Upgrade to a release after 15.023.20070
Interim mitigation

Update Adobe Acrobat Reader to the latest version to patch the memory corruption vulnerability in the renderer component.

Fix this in Acrobat Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-3018 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