CVE-2018-12849
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 versions 2018.011.20058 and earlier, 2017.011.30099 and earlier, and 2015.006.30448 and earlier have an out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.
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 confidenceAdobe Acrobat and Reader contain an out-of-bounds read vulnerability that allows reading memory outside allocated buffers. Successful exploitation enables attackers to extract sensitive information from the application's memory space. The vulnerability affects multiple older version branches across 2015, 2017, and 2018 releases.
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.30448>= 15.008.20082, <= 18.011.20058>= 17.011.30059, <= 17.011.30099>= 15.006.30060, <= 15.006.30448>= 15.008.20082, <= 18.011.20058>= 17.011.30059, <= 17.011.30099CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 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 Reader (or About Adobe Acrobat) to view the version number. Alternatively, check Add/Remove Programs (Windows) or Applications folder (Mac) for installed Adobe software.Affected if Either Adobe Acrobat DC or Adobe Acrobat Reader DC is present on the system
-
Verify exact version numberLocate the exact four-part version number displayed in the About dialog (for example: 15.006.30060 or 18.011.20058). Note the complete version string including all four digit groups.Affected if The displayed version matches any of the affected ranges listed in the CVE
-
Compare against affected version rangesCheck if your installed version falls within: 15.006.30060 to 15.006.30448; 15.008.20082 to 18.011.20058; or 17.011.30059 to 17.011.30099. These ranges cover 2015, 2017, and 2018 release branches.Affected if The installed version number is greater than or equal to the minimum and less than or equal to the maximum of any affected range
-
Confirm product type and update statusDetermine whether the installation is the Continuous track (DC) version, as the CVE specifically affects DC variants. Check if automatic updates have already been applied, which may have upgraded the version beyond the affected ranges.Affected if The product is Acrobat DC or Reader DC, and the version remains within an affected range indicating no patch has been applied
A system is affected if Adobe Acrobat DC or Adobe Acrobat Reader DC is installed with a version number falling within any of the specified ranges (15.006.30060-15.006.30448, 15.008.20082-18.011.20058, or 17.011.30059-17.011.30099).
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.
From vendor dataApply the vendor security update by upgrading to a patched version of Adobe Acrobat or Reader. Organizations should identify all deployed instances of affected versions and deploy the latest security patches from Adobe.
- 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-12849 — 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-12849 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