dbcve.org
Acrobat DcApplication · Adobe

CVE-2018-12843

MEDIUM · 5.5 CVSS v3.0 Published 2018-10-12
Fix available
A fix is available. Upgrade to after 18.011.20063 or later.
See remediation →
58/100
Remediation priority · Elevated
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 read vulnerability. Successful exploitation could lead to information disclosure.

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 and Reader versions 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier contain an out-of-bounds read vulnerability that could allow an attacker to read sensitive information from memory by triggering the vulnerability through a specially crafted PDF file.

MitigationUpdate Adobe Acrobat and Reader to the latest vendor-patched versions to remediate this vulnerability. Prioritize updating systems that handle sensitive or confidential 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
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 checks

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

  1. Check if Adobe Acrobat or Reader is installed
    On Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat or HKEY_LOCAL_MSOFTWARE\Adobe\Adobe Acrobat Reader DC. If these keys exist, the product is installed.
    Affected if Neither key exists under HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\ - the system is not affected.
  2. Locate the installed executable
    Find the Adobe Acrobat or Reader executable file. Common paths: C:\Program Files\Adobe\Acrobat DC\AcroRd32.exe or C:\Program Files (x86)\Adobe\Acrobat Reader DC\AcroRd32.exe. Right-click the file, select Properties, and view the Details tab for version information.
    Affected if The executable is not found at these common paths.
  3. Extract the installed version number
    Read the Product Version field from the executable's Details tab, or run: wmic datafile where name='C:\Program Files\Adobe\Acrobat DC\AcroRd32.exe' get Version. Note the full version string (for example: 18.011.20063).
    Affected if Cannot retrieve a version number - product may not be installed or accessible.
  4. Compare against affected version ranges
    Check if your version falls within: 15.006.30060 to 15.006.30452, 15.008.20082 to 18.011.20063, or 17.011.30059 to 17.011.30102. For Acrobat DC Classic 2015, check 15.x versions. For Acrobat DC Continuous, check 18.x versions. For Acrobat 2017, check 17.x versions.
    Affected if The installed version is within any of these three ranges - the system is affected.
  5. Verify Reader vs Pro version
    Determine if the installed product is Adobe Acrobat Reader DC (free version) or Adobe Acrobat Pro DC (paid version) by checking the product name in Add/Remove Programs or the executable file name. Both have the same affected versions.
    Affected if The installed product is either Reader DC or Acrobat DC and version falls in affected ranges.

A system is affected if Adobe Acrobat DC or Adobe Acrobat Reader DC is installed with a version number matching 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 vendor-patched versions to remediate this vulnerability. Prioritize updating systems that handle sensitive or confidential documents.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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