Acrobat DcApplication · Adobe

CVE-2018-12795

HIGH · 7.5 CVSS v3.0 Published 2018-07-20
Fix available
A fix is available. Upgrade to after 18.011.20040 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions 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

Out-of-bounds read vulnerability in Adobe Acrobat and Reader affecting versions 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier. The vulnerability allows reading memory beyond allocated boundaries, potentially exposing sensitive information through memory disclosure.

MitigationApply the vendor-supplied security patches from Adobe to update Adobe Acrobat and Reader to the latest version or the specific patched versions referenced in the security advisory.

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.30418>= 15.008.20082, <= 18.011.20040>= 17.011.30059, <= 17.011.30080
Acrobat Reader DcApplication
Affected:>= 15.006.30060, <= 15.006.30418>= 15.008.20082, <= 18.011.20040>= 17.011.30059, <= 17.011.30080

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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_MACHINE\SOFTWARE\Adobe\Adobe Acrobat Reader, or check C:\Program Files\Adobe for the Acrobat or Reader folder.
    Affected if Either Adobe Acrobat DC or Adobe Acrobat Reader DC is present on the system
  2. Determine the installed version of Adobe Acrobat DC
    In Windows Registry, go to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\DC\InstallProperties and look at the 'Version' value, or right-click the Acrobat executable in C:\Program Files\Adobe\Acrobat DC\Acrobat and select Properties to view the File Version.
    Affected if The displayed version falls within any of these ranges: 15.006.30060-15.006.30418, 15.008.20082-18.011.20040, or 17.011.30059-17.011.30080
  3. Determine the installed version of Adobe Acrobat Reader DC
    In Windows Registry, go to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat Reader\DC\InstallProperties and look at the 'Version' value, or right-click the Reader executable in C:\Program Files\Adobe\Acrobat Reader DC\ and select Properties to view the File Version.
    Affected if The displayed version falls within any of these ranges: 15.006.30060-15.006.30418, 15.008.20082-18.011.20040, or 17.011.30059-17.011.30080

The system is affected if Adobe Acrobat DC or Adobe Acrobat Reader DC is installed with a version number matching one of the three vulnerable ranges listed in the CVE.

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.20040
Interim mitigation

Apply the vendor-supplied security patches from Adobe to update Adobe Acrobat and Reader to the latest version or the specific patched versions referenced in the security advisory.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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