CVE-2018-12792
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 Use-after-free 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 · high confidenceA use-after-free vulnerability exists in Adobe Acrobat and Reader versions 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier. Successful exploitation allows an attacker to achieve arbitrary code execution in the context of the current user.
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 productOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat (or Reader). Alternatively, on Windows check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\DC\Version or on macOS check the application bundle info.Affected if The displayed version falls within any of these ranges: 15.006.30060 to 15.006.30418, 15.008.20082 to 18.011.20040, or 17.011.30059 to 17.011.30080.
-
Confirm product editionVerify whether the installed product is Adobe Acrobat DC or Adobe Acrobat Reader DC, as both are affected. Reader DC is typically free and used for viewing PDFs, while Acrobat DC is the paid version with editing capabilities.Affected if The product is Adobe Acrobat DC or Adobe Acrobat Reader DC within the affected version ranges.
-
Verify version numbering schemeCheck if the installed version follows the classic track (15.x.xxxxx) or continuous track (17.x.xxxxx or 18.x.xxxxx) release format. The continuous track versions use 3-digit build numbers (e.g., 18.011.20040).Affected if The version is exactly 15.006.30418 or earlier, 15.008.20082 to 18.011.20040 inclusive, or 17.011.30080 or earlier.
If Adobe Acrobat DC or Adobe Acrobat Reader DC is installed and its version falls within the ranges 15.006.30060-15.006.30418, 15.008.20082-18.011.20040, or 17.011.30059-17.011.30080, the environment is affected by CVE-2018-12792.
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 · scopedApply vendor-supplied security updates to upgrade Adobe Acrobat and Reader to patched versions beyond those listed.
Adobe Acrobat/Reader DC 2018 version 18.011.20041 or later (Classic 2017: 17.011.30081 or later; Classic 2015: 15.006.30419 or later)
- Identify the currently installed Adobe Acrobat or Reader version by opening the application, then navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- Determine which product line (2015, 2017, or 2018) your installation belongs to based on the version number shown.
- For Adobe Acrobat DC (Continuous): If version is 18.011.20040 or earlier, upgrade to version 18.011.20041 or later.
- For Adobe Acrobat DC (Classic 2017): If version is 17.011.30080 or earlier, upgrade to version 17.011.30081 or later.
- For Adobe Acrobat DC (Classic 2015): If version is 15.006.30418 or earlier, upgrade to version 15.006.30419 or later.
- For Adobe Reader DC: Apply the corresponding Reader update using the same version thresholds as Acrobat.
- Download the appropriate updated version from the official Adobe website (get.adobe.com/reader for Reader, or adobe.com for Acrobat), or use the built-in update checker via Help > Check for Updates.
- Install the update and restart the application to complete the remediation.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12792 — 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-12792 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