CVE-2018-12758
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 an Out-of-bounds write 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 confidenceAn out-of-bounds write vulnerability in Adobe Acrobat and Reader versions 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier allows attackers to write data outside the bounds of allocated memory buffers, enabling 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.
-
Confirm Adobe Acrobat or Reader is installedWindows: Open Control Panel > Programs and Features, look for 'Adobe Acrobat DC' or 'Adobe Acrobat Reader DC'. Mac: Open Applications folder and check for Adobe Acrobat or Reader.Affected if Neither Adobe Acrobat nor Adobe Reader is installed, the system is not affected by this CVE.
-
Determine the exact installed version numberWindows: Right-click the application in Programs and Features, select Properties, look at the Version field. Or open the application, go to Help > About Adobe Acrobat/Reader. Mac: Right-click application in Applications, select Get Info, or open app and go to Help > About.Affected if The installed version cannot be determined, the vulnerability status is unknown.
-
Compare your version against affected rangesCompare the installed version number to these affected ranges: 15.006.30060 through 15.006.30418, 15.008.20082 through 18.011.20040, and 17.011.30059 through 17.011.30080. Note that version 15.008.20082 is the lower bound of the 2018 track despite using the 15.x baseline.Affected if The installed version falls within any of the listed version ranges, the installation is vulnerable.
-
Verify the product track (Classic or Continuous) if needed for remediationIf version is ambiguous between tracks, check Help > About - Continuous track versions typically have longer version numbers. The 15.008.x and 18.x versions are Continuous track, while 15.006.x and 17.x are Classic track.Affected if Version is within affected range regardless of track - this check is informational for reporting purposes only.
A system is affected if Adobe Acrobat DC or Adobe Acrobat Reader DC is installed with a version number matching any of the three ranges: 15.006.30060-15.006.30418, 15.008.20082-18.011.20040, or 17.011.30059-17.011.30080.
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 as specified in Adobe security bulletins to address the out-of-bounds write vulnerability.
Adobe Acrobat/Reader 2015.006.30506+, 2017.011.30094+, or 2018.011.20055+ (or latest continuous track version)
- 1. Verify current Adobe Acrobat or Reader version by opening the application, selecting Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. Determine which release track your current version belongs to: 2015.x, 2017.x, or 2018.x.
- 3. For Adobe Acrobat DC or Acrobat Reader DC: Download the latest version from the official Adobe website at get.adobe.com/reader or get.adobe.com/acrobat.
- 4. If using the continuous track, ensure updates are enabled and run Help > Check for Updates to receive version 2018.011.20055 or later.
- 5. If using the classic track: For 2015.x users, upgrade to version 2015.006.30506 or later. For 2017.x users, upgrade to version 2017.011.30094 or later. For 2018.x users, upgrade to version 2018.011.20055 or later.
- 6. Restart the application after the update completes.
- 7. Verify the installed version is no longer within any of the affected ranges: not 15.006.30060 through 15.006.30418, not 15.008.20082 through 18.011.20040, and not 17.011.30059 through 17.011.30080.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12758 — 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-12758 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