dbcve.org
Acrobat DcApplication · Adobe

CVE-2018-15943

MEDIUM · 5.5 CVSS v3.0 Published 2018-10-12
Fix available
A fix is available. Upgrade to after 18.011.20063 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
Adobe Acrobat and Reader versions 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 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 · moderate confidence

This is an out-of-bounds read vulnerability in Adobe Acrobat and Reader. The vulnerability exists in specific versions (2018.011.20063 and earlier, 2017.011.30102 and earlier, 2015.006.30452 and earlier) and could allow an attacker to read sensitive information from memory beyond allocated buffers.

MitigationApply the vendor security update from Adobe to patch the vulnerable Acrobat/Reader installations. Users should update to version 2018.011.20070 or later for the 2018 release track, or the corresponding patched versions for other affected release tracks.

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
Acrobat DcApplication
Affected:>= 15.006.30060, <= 15.006.30452>= 15.008.20082, <= 18.011.20063>= 17.011.30059, <= 17.011.30102
Acrobat Reader DcApplication
Affected:>= 15.006.30060, <= 15.006.30452>= 15.008.20082, <= 18.011.20063>= 17.011.30059, <= 17.011.30102

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Adobe Acrobat or Reader is installed
    Look for Adobe Acrobat DC or Adobe Acrobat Reader DC in the list of installed programs, or check common installation paths such as C:\Program Files\Adobe\Acrobat DC\ or C:\Program Files (x86)\Adobe\Acrobat Reader DC\
    Affected if Either Adobe Acrobat DC or Adobe Acrobat Reader DC is present on the system
  2. Determine the installed product version
    Open the application, go to Help > About Adobe Acrobat/Reader, or check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\DC\Version or HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\DC\Version
    Affected if A version number is displayed that matches any of the affected release tracks (15.x, 17.x, or 18.x)
  3. Compare the installed version against affected ranges
    Match the installed version number to the following vulnerable ranges: 15.006.30060 through 15.006.30452; 15.008.20082 through 18.011.20063; 17.011.30059 through 17.011.30102
    Affected if The installed version falls within any of these three version ranges
  4. Confirm the product track (Continuous or Classic)
    Check if the version starts with 15.006, 15.008, 17.011, or 18.011 to identify the release track and confirm it aligns with the affected version ranges provided
    Affected if The version follows the 15.x, 17.x, or 18.x release track and matches the affected ranges above

A user is affected if Adobe Acrobat DC or Adobe Acrobat Reader DC is installed with a version number that falls within any of the three vulnerable ranges: 15.006.30060-15.006.30452, 15.008.20082-18.011.20063, or 17.011.30059-17.011.30102.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 18.011.20063
Interim mitigation

Apply the vendor security update from Adobe to patch the vulnerable Acrobat/Reader installations. Users should update to version 2018.011.20070 or later for the 2018 release track, or the corresponding patched versions for other affected release tracks.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-15943 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-15943 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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