dbcve.org
Acrobat DcApplication · Adobe

CVE-2018-5027

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 · high confidence

An out-of-bounds read vulnerability in Adobe Acrobat and Reader allows attackers to read memory contents beyond allocated buffers, potentially exposing sensitive information. The vulnerability affects multiple older versions across three major release branches (2015, 2017, and 2018).

MitigationUpdate Adobe Acrobat and Reader to the latest version or apply the relevant security patches from Adobe's official security bulletins.

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 DC is installed
    On Windows, open Control Panel > Programs and Features and look for 'Adobe Acrobat DC' or 'Adobe Acrobat Reader DC'. Alternatively, launch the application and go to Help > About Adobe Acrobat DC (or Reader).
    Affected if Neither Adobe Acrobat DC nor Adobe Acrobat Reader DC is installed (not affected).
  2. Identify the exact installed version
    In the application, go to Help > About Adobe Acrobat DC (or Reader). The version number displays in the format XX.XXX.XXXXX.X (for example, 15.006.30060). Note the full version string exactly as shown.
    Affected if The installed version cannot be determined or the product is not Adobe Acrobat/Reader DC (detection inconclusive).
  3. Compare version against affected range 1
    Check if your version falls between 15.006.30060 and 15.006.30418 (inclusive). Compare each numeric segment: 15.006.30060 <= your version <= 15.006.30418.
    Affected if Version is within this range (15.006.30060 to 15.006.30418) - likely affected.
  4. Compare version against affected range 2
    Check if your version falls between 15.008.20082 and 18.011.20040 (inclusive). Compare each numeric segment: 15.008.20082 <= your version <= 18.011.20040.
    Affected if Version is within this range (15.008.20082 to 18.011.20040) - likely affected.
  5. Compare version against affected range 3
    Check if your version falls between 17.011.30059 and 17.011.30080 (inclusive). Compare each numeric segment: 17.011.30059 <= your version <= 17.011.30080.
    Affected if Version is within this range (17.011.30059 to 17.011.30080) - likely affected.

If Adobe Acrobat DC or Reader DC is installed and the installed version matches any of the three affected ranges, the environment is vulnerable to CVE-2018-5027.

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 version or apply the relevant security patches from Adobe's official security bulletins.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing2.0 h
  • Review / QA1.0 h
12.0 hours of engineering $2,160
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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