dbcve.org
Acrobat DcApplication · Adobe

CVE-2018-12775

HIGH · 7.5 CVSS v3.0 Published 2018-09-25
Fix available
A fix is available. Upgrade to after 18.011.20058 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 versions 2018.011.20058 and earlier, 2017.011.30099 and earlier, and 2015.006.30448 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

This is an out-of-bounds read vulnerability in Adobe Acrobat and Reader. The flaw allows a specially crafted PDF file to read memory outside allocated buffer boundaries, potentially exposing sensitive information from the application's memory space.

MitigationUpdate Adobe Acrobat and Reader to versions newer than 2018.011.20058, 2017.011.30099, and 2015.006.30448 respectively. Users should verify they have the latest patches from Adobe.

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.30448>= 15.008.20082, <= 18.011.20058>= 17.011.30059, <= 17.011.30099
Acrobat Reader DcApplication
Affected:>= 15.006.30060, <= 15.006.30448>= 15.008.20082, <= 18.011.20058>= 17.011.30059, <= 17.011.30099

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. Verify Adobe Acrobat or Reader is installed
    Check for the presence of Adobe Acrobat or Reader in typical installation locations: C:\Program Files\Adobe\Acrobat DC\ or C:\Program Files (x86)\Adobe\Acrobat 2015\ or C:\Program Files\Adobe\Acrobat 2017\. On macOS, check /Applications for Adobe Acrobat or Adobe Reader apps.
    Affected if Adobe Acrobat or Adobe Reader is not installed on the system, the vulnerability does not apply.
  2. Determine the installed product name and version
    Open Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat/Reader to display the exact version number and build (e.g., 18.011.20058). Alternatively, check the Windows registry under HKLM\SOFTWARE\Adobe\Acrobat DC\InstallProperties for 'Version' and 'Build' values, or HKLM\SOFTWARE\Adobe\Acrobat 2017\ for version 2017 products.
    Affected if The product name is Adobe Acrobat DC or Adobe Acrobat Reader DC (or 2015/2017 variants).
  3. Compare installed version against affected ranges
    Match the installed version number (e.g., 18.011.20058) against these affected ranges: 15.006.30060-15.006.30448, 15.008.20082-18.011.20058, and 17.011.30059-17.011.30099. The version format varies by track: Classic uses 15.x.x, Continuous uses 17.x or 18.x.
    Affected if The installed version falls within any of these ranges, the system is potentially affected by this out-of-bounds read vulnerability.
  4. Verify the PDF handling feature is in use
    The vulnerability triggers when opening a specially crafted malicious PDF file. Check if the application is configured to open PDF files automatically or if users commonly open PDF attachments/documents.
    Affected if Users open PDF files from untrusted sources using the affected Adobe product, making exploitation possible.

A system is affected if Adobe Acrobat DC or Adobe Acrobat Reader DC is installed with a version number matching any of the three vulnerable ranges: 15.006.30060 through 15.006.30448, 15.008.20082 through 18.011.20058, or 17.011.30059 through 17.011.30099.

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

Update Adobe Acrobat and Reader to versions newer than 2018.011.20058, 2017.011.30099, and 2015.006.30448 respectively. Users should verify they have the latest patches from Adobe.

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-12775 — 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-12775 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