CVE-2018-4879
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 · uneditedAn 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. The vulnerability is caused by the computation that writes data past the end of the intended buffer; the computation is part of the image conversion module that processes Enhanced Metafile Format Plus (EMF+) data. An attacker can potentially leverage the vulnerability to corrupt sensitive data or execute arbitrary code.
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 confidenceBuffer overflow vulnerability in Adobe Acrobat Reader's image conversion module that processes Enhanced Metafile Format Plus (EMF+) data. The computation writes data past the end of the intended buffer, potentially allowing arbitrary code execution.
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>= 17.0, <= 17.011.30070>= -, <= 18.009.20050>= 15.0, <= 15.006.30394>= 17.0, <= 17.011.30070>= -, <= 18.009.20050>= 15.0, <= 15.006.30394CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Locate installed Adobe Acrobat or Reader versionOpen Adobe Acrobat/Reader, go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). Alternatively, check Add/Remove Programs or the registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-xxxx} for the DisplayVersion value.Affected if The displayed version number falls within the affected ranges: 17.0 through 17.011.30070, 18.0 through 18.009.20050, or 15.0 through 15.006.30394.
-
Identify the product variantConfirm whether the installed product is standard Adobe Acrobat/Reader or the Desktop (DC) variant. The DC versions have separate version ranges from the classic versions.Affected if The product is Adobe Acrobat Reader DC or Adobe Acrobat DC and the version is at or below 18.009.20050 or between 15.0 and 15.006.30394.
-
Determine if image conversion feature is accessibleAttempt to open an image file (JPG, PNG, BMP) in the installed Adobe product, or check if the product can be used to convert images to PDF. This vulnerability exists in the image conversion module.Affected if The product successfully opens or converts image files, indicating the vulnerable module is present and functional.
You are affected if the installed Adobe Acrobat or Reader version falls within any of the listed vulnerable ranges and the image conversion feature is available on your system.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpdate Adobe Acrobat Reader to the latest patched version that addresses this vulnerability.
Adobe Acrobat Reader/Acrobat 2018.011.20033 or later (2018 track); 2017.011.30102 or later (2017 track); 2015.006.30417 or later (2015 track); or latest Continuous track version
- 1. Verify the currently installed Adobe Acrobat or Acrobat Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. Identify the product line and version family (2015, 2017, or 2018) from the version number.
- 3. For Adobe Acrobat Reader DC or Acrobat DC (Continuous track): Update to version 18.011.20033 or later via Help > Check for Updates, or download the latest version from the Adobe website.
- 4. For Adobe Acrobat Reader 2017 or Acrobat 2017 (Classic track): Update to version 2017.011.30102 or later.
- 5. For Adobe Acrobat Reader 2015 or Acrobat 2015 (Classic track): Update to version 2015.006.30417 or later.
- 6. Restart the application after installing the update.
- 7. Verify the update was successful by checking Help > About again to confirm the version is beyond the affected ranges.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-4879 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-4879 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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