dbcve.org
AcrobatApplication · Adobe

CVE-2018-4906

MEDIUM · 6.5 CVSS v3.0 Published 2018-02-27
Fix available
A fix is available. Upgrade to after 18.009.20050 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
An issue was discovered in Adobe Acrobat Reader 2018.009.20050 and earlier versions, 2017.011.30070 and earlier versions, 2015.006.30394 and earlier versions. This vulnerability occurs as a result of computation that reads data that is past the end of the target buffer; the computation is part of the image conversion module that handles Enhanced Metafile Format Plus (EMF+) data related to graphic object image attributes. A successful attack can lead to sensitive data exposure.

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

This is an out-of-bounds read vulnerability in Adobe Acrobat Reader's image conversion module. The vulnerability occurs when parsing Enhanced Metafile Format Plus (EMF+) data related to graphic object image attributes, allowing an attacker to read data past the end of the target buffer. Successful exploitation can lead to sensitive data exposure.

MitigationUpdate Adobe Acrobat Reader to the latest version (or at minimum a version beyond 2018.009.20050/2017.011.30070/2015.006.30394 depending on the release line in use) to remediate this out-of-bounds read vulnerability in the EMF+ image parsing module.

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
AcrobatApplication
Affected:>= 17.0, <= 17.011.30070
Acrobat DcApplication
Affected:>= -, <= 18.009.20050>= 15.0, <= 15.006.30394
Acrobat ReaderApplication
Affected:>= 17.0, <= 17.011.30070
Acrobat Reader DcApplication
Affected:>= -, <= 18.009.20050>= 15.0, <= 15.006.30394

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. Verify Adobe Acrobat or Reader is installed
    On Windows, open Programs and Features or run: wmic product get name,version | findstr /i "Acrobat"
    Affected if Adobe Acrobat or Adobe Acrobat Reader appears in the installed software list
  2. Obtain the exact installed version number
    On Windows, right-click the Adobe Acrobat/Reader icon, select Properties, and check the Details tab for the Product Version; alternatively, run: wmic product where "name like 'Adobe Acrobat%'" get version
    Affected if A version number is returned that can be compared against the affected ranges
  3. Confirm the product variant and release line
    Identify whether the installation is Adobe Acrobat (standard), Adobe Acrobat Dc, Adobe Acrobat Reader, or Adobe Acrobat Reader Dc, and determine if it is a 2015 (15.x), 2017 (17.x), or 2018 (18.x) release line
    Affected if The product matches one of the four affected variants listed in the CVE
  4. Compare installed version against affected ranges
    For Acrobat/Reader 2015 (15.x): check if version is between 15.0.0 and 15.006.30394 inclusive; for 2017 (17.x): check if version is between 17.0.0 and 17.011.30070 inclusive; for 2018 (18.x): check if version is 18.009.20050 or lower
    Affected if The installed version falls within any of the affected version ranges specified in the CVE

A user is affected if Adobe Acrobat or Acrobat Reader is installed with a version matching 15.0 through 15.006.30394, 17.0 through 17.011.30070, or up to 18.009.20050, and the application is used to open or process documents containing EMF+ image data.

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

Update Adobe Acrobat Reader to the latest version (or at minimum a version beyond 2018.009.20050/2017.011.30070/2015.006.30394 depending on the release line in use) to remediate this out-of-bounds read vulnerability in the EMF+ image parsing module.

Fix this in Acrobat 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-4906 — 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-4906 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