CVE-2018-5025
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 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 · moderate confidenceThis is an out-of-bounds read vulnerability in Adobe Acrobat and Reader affecting multiple legacy versions (2018.011.20040 and earlier, 2017.011.30080 and earlier, 2015.006.30418 and earlier). The vulnerability allows reading memory beyond allocated buffer boundaries, potentially exposing sensitive information to remote attackers without authentication.
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
- 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 the installed Adobe productOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat/Reader DC to see the exact product name and version number displayed in the dialog windowAffected if The product is Adobe Acrobat DC or Adobe Acrobat Reader DC (Classic or Continuous track)
-
Locate the version information from the application fileOn Windows, right-click the executable (Acrobat.exe or Acrord32.exe) in the installation directory, select Properties, and view the Details tab for the Product Version field. On macOS, right-click the application in Applications, select Get Info, and view the Version fieldAffected if The installed version falls within any of the vulnerable ranges
-
Compare the installed version against vulnerable rangesRecord the full version number (for example: 15.006.30418 or 17.011.30080) and compare it to these ranges: 15.006.30060-15.006.30418, 15.008.20082-18.011.20040, or 17.011.30059-17.011.30080Affected if The installed version is greater than or equal to the lower bound AND less than or equal to the upper bound of any vulnerable range listed
-
Verify the product track and update channelCheck if the installation is the Continuous track (updates automatically) or Classic track by looking at the version number prefix: versions starting with 15.x or 17.x or 18.x indicate specific release tracks. The About dialog also displays the track typeAffected if The product uses a track version within the affected ranges
If Adobe Acrobat DC or Adobe Acrobat Reader DC is installed with a version matching any of the three vulnerable 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 this out-of-bounds read vulnerability.
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 Adobe security update to upgrade to a patched version of Adobe Acrobat and Reader beyond the vulnerable releases specified. Organizations should prioritize updating systems handling sensitive documents.
- 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-5025 — 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-5025 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