CVE-2018-12784
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 · uneditedAdobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have a Buffer Errors vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.
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 confidenceA buffer errors vulnerability in Adobe Acrobat and Reader allows attackers to corrupt memory and execute arbitrary code by enticing users to open specially crafted PDF files. The vulnerability affects versions 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier.
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>= 15.006.30060, <= 15.006.30418>= 15.008.20082, <= 18.011.20040>= 17.011.30059, <= 17.011.30080>= 15.006.30060, <= 15.006.30418>= 15.008.20082, <= 18.011.20040>= 17.011.30059, <= 17.011.30080CVSS 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.
-
Identify installed Adobe Acrobat DC versionOpen Adobe Acrobat DC, go to Help > About Adobe Acrobat DC, or run: Registry key HKLM\SOFTWARE\Adobe\Adobe Acrobat\DC\Version (or HKLM\SOFTWARE\WOW6432Node\Adobe\Adobe Acrobat\DC\Version on 64-bit)Affected if Version number is 15.006.30060 through 15.006.30418, 15.008.20082 through 18.011.20040, or 17.011.30059 through 17.011.30080
-
Identify installed Adobe Acrobat Reader DC versionOpen Adobe Acrobat Reader DC, go to Help > About Adobe Acrobat Reader DC, or run: Registry key HKLM\SOFTWARE\Adobe\Acrobat Reader\DC\Version (or HKLM\SOFTWARE\WOW6432Node\Adobe\Acrobat Reader\DC\Version on 64-bit)Affected if Version number is 15.006.30060 through 15.006.30418, 15.008.20082 through 18.011.20040, or 17.011.30059 through 17.011.30080
-
Determine if vulnerable software is actively usedCheck for recent PDF opening activity or scheduled tasks associated with Adobe Acrobat/Reader, or query installed programs list for Adobe Acrobat Dc or Adobe Acrobat Reader Dc entries within affected version rangesAffected if Adobe Acrobat Dc or Reader Dc is installed with a version in the affected ranges and the software is used to open PDF files
You are affected if Adobe Acrobat Dc or Adobe Acrobat Reader Dc is installed with a version within 15.006.30060-15.006.30418, 15.008.20082-18.011.20040, or 17.011.30059-17.011.30080, as these versions contain the memory corruption flaw exploitable via malicious PDF files.
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 and Reader to the latest patched versions available from Adobe's official security bulletin. Prioritize patching given the critical CVSS 9.8 rating and public exploit potential.
Adobe Acrobat/Reader DC 2018.011.20055 or later (or the latest 2020/2021 version)
- 1. Close all instances of Adobe Acrobat or Adobe Acrobat Reader DC
- 2. Back up any important PDF files and settings as a precautionary measure
- 3. Download the latest version of Adobe Acrobat DC or Adobe Acrobat Reader DC from the official Adobe website (https://get.adobe.com/reader/)
- 4. Run the installer and follow the prompts to complete the installation
- 5. Restart your computer after installation completes
- 6. Verify the installed version by opening Adobe Acrobat/Reader and checking Help > About Adobe Acrobat/Reader
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12784 — 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-12784 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