dbcve.org
Acrobat DcApplication · Adobe

CVE-2018-12803

MEDIUM · 6.5 CVSS v3.0 Published 2018-07-20
Fix available
A fix is available. Upgrade to after 18.011.20040 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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 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

This is an out-of-bounds read vulnerability in Adobe Acrobat and Reader that allows reading memory outside the intended buffer boundaries. Successful exploitation could expose sensitive information from the application's memory space. The vulnerability affects multiple version families (2015, 2017, and 2018) across the specified version boundaries.

MitigationUpdate Adobe Acrobat and Reader to the latest patched versions beyond 2018.011.20040, 2017.011.30080, and 2015.006.30418 respectively. In enterprise environments, use Adobe's patch management tools or standard software deployment mechanisms to ensure complete coverage.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/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. Confirm Adobe Acrobat or Reader installation
    Open the application and navigate to Help > About Adobe Acrobat/Reader DC, or check Programs and Features in Control Panel for installed Adobe software.
    Affected if Adobe Acrobat DC or Adobe Acrobat Reader DC is present on the system.
  2. Identify the exact product version
    In the application, go to Help > About Adobe Acrobat/Reader DC and note the exact version number displayed (for example: 18.011.20040). For command-line check, examine the registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat\DC\Version or HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AdobeReader\DC\Version.
    Affected if The installed version falls within the 15.x, 17.x, or 18.x branch families.
  3. Compare version against affected ranges for 2015 versions
    If the version starts with 15.006.x, check if it is between 15.006.30060 and 15.006.30418 inclusive. If the version starts with 15.008.x, check if it is between 15.008.20082 and the upper bound for that branch.
    Affected if Version is 15.006.30060 through 15.006.30418, or 15.008.20082 through the upper 15.x boundary.
  4. Compare version against affected ranges for 2017 versions
    If the version starts with 17.011.x, check if it falls between 17.011.30059 and 17.011.30080 inclusive.
    Affected if Version is 17.011.30059 through 17.011.30080.
  5. Compare version against affected ranges for 2018 versions
    If the version starts with 18.x, check if it is between 18.011.20082 (or the relevant 18.x lower bound) and 18.011.20040 inclusive. Note: Ensure the full version number is within the 18.011.x branch and does not exceed 18.011.20040.
    Affected if Version is within the 18.x branch up to and including 18.011.20040.

The 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-15.006.30418, 15.008.20082-15.x upper bound, 17.011.30059-17.011.30080, or 18.x up to 18.011.20040.

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

Update Adobe Acrobat and Reader to the latest patched versions beyond 2018.011.20040, 2017.011.30080, and 2015.006.30418 respectively. In enterprise environments, use Adobe's patch management tools or standard software deployment mechanisms to ensure complete coverage.

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