dbcve.org
Acrobat DcApplication · Adobe

CVE-2018-12847

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 a heap overflow 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

Heap overflow vulnerability in Adobe Acrobat and Reader affecting versions 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier. Successful exploitation allows arbitrary code execution.

MitigationUpdate Adobe Acrobat and Reader to the latest patched versions available from Adobe. Prioritize updating 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. Check if Adobe Acrobat or Reader is installed
    On Windows, open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed software and their versions.
    Affected if Adobe Acrobat DC, Adobe Acrobat Reader DC, or similar Adobe Reader products appear in the installed programs list.
  2. Locate the exact installed version of Adobe Acrobat or Reader
    Open Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). Alternatively, on Windows, check the registry key HKLM\Software\Adobe\Acrobat\DC\Version or HKLM\Software\Adobe\Acrobat\Reader\DC\Version, or examine the executable properties of AcroRd32.exe or AcroBroker.exe in the installation folder.
    Affected if A version number is displayed or found in registry/file properties.
  3. Compare your installed version against affected ranges
    If your version starts with 15.x, check if it falls between 15.006.30060 and 15.006.30452, OR between 15.008.20082 and 15.011.20063. If version 17.x, check between 17.011.30059 and 17.011.30102. If version 18.x, check up to 18.011.20063. Note the three-digit build number after the second decimal (e.g., 20063 in 18.011.20063).
    Affected if Your version matches any of these ranges: 15.006.30060-15.006.30452, 15.008.20082-18.011.20063, or 17.011.30059-17.011.30102.
  4. Identify the specific Adobe product variant installed
    Distinguish between Adobe Acrobat DC (paid/professional) and Adobe Acrobat Reader DC (free viewer) using the program name from step 1 or the registry key path. Both product types share the same version numbering and are both affected.
    Affected if Either Adobe Acrobat DC or Adobe Acrobat Reader DC is installed within the affected version ranges.

You are affected if Adobe Acrobat DC or Adobe Acrobat Reader DC is installed with a version number that falls within any of the listed 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 available from Adobe. Prioritize updating systems that process untrusted PDF documents.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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