dbcve.org
Acrobat DcApplication · Adobe

CVE-2018-12759

HIGH · 7.8 CVSS v3.0 Published 2018-10-12
Fix available
A fix is available. Upgrade to after 18.011.20063 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 and Reader versions 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier have an out-of-bounds write vulnerability. 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 confidence

Adobe Acrobat and Reader contain an out-of-bounds write vulnerability where memory can be written beyond allocated buffer boundaries. This memory corruption can be leveraged by attackers to achieve arbitrary code execution on vulnerable systems.

MitigationUpdate Adobe Acrobat and Reader to the latest patched versions released by Adobe to remediate this vulnerability. Prioritize systems that process untrusted PDF documents.

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
Acrobat DcApplication
Affected:>= 15.006.30060, <= 15.006.30452>= 15.008.20082, <= 18.011.20063>= 17.011.30059, <= 17.011.30102
Acrobat Reader DcApplication
Affected:>= 15.006.30060, <= 15.006.30452>= 15.008.20082, <= 18.011.20063>= 17.011.30059, <= 17.011.30102

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 installation in Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Acrobat.exe, or look in Program Files for Adobe Acrobat or Adobe Acrobat Reader folders
    Affected if Either Adobe Acrobat DC or Adobe Acrobat Reader DC is present on the system
  2. Determine the installed version number
    Open Windows Registry and navigate to HKLM\SOFTWARE\Adobe\Adobe Acrobat\DC\InstallVersion, read the 'Version' value; alternatively, right-click the Acrobat or Reader executable in Program Files, select Properties, and view the Details tab for the Product Version
    Affected if Unable to retrieve a version number - the product may be installed but version cannot be confirmed
  3. Compare version against affected range 15.006.30060 through 15.006.30452
    If installed version begins with 15.006, check if the full version number (for example, 15.006.304xx) falls between 15.006.30060 and 15.006.30452 inclusive
    Affected if Installed version is 15.006.30060 through 15.006.30452 inclusive
  4. Compare version against affected range 15.008.20082 through 18.011.20063
    If installed version begins with 15.008, 16.x, 17.x, or 18.x, verify whether the version falls between 15.008.20082 and 18.011.20063 inclusive
    Affected if Installed version is 15.008.20082 through 18.011.20063 inclusive
  5. Compare version against affected range 17.011.30059 through 17.011.30102
    If installed version begins with 17.011, check if the full version number falls between 17.011.30059 and 17.011.30102 inclusive
    Affected if Installed version is 17.011.30059 through 17.011.30102 inclusive

The system is affected if Adobe Acrobat DC or Adobe Acrobat Reader DC is installed with a version matching any of the three affected ranges: 15.006.30060-15.006.30452, 15.008.20082-18.011.20063, or 17.011.30059-17.011.30102

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 18.011.20063
Interim mitigation

Update Adobe Acrobat and Reader to the latest patched versions released by Adobe to remediate this vulnerability. Prioritize systems that process untrusted PDF documents.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-12759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2018-12759 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