dbcve.org
AcrobatApplication · Adobe

CVE-2016-7019

CRITICAL · 9.8 CVSS v3.0 Published 2016-10-13
Fix available
A fix is available. Upgrade to after 15.017.20053 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Reader and Acrobat before 11.0.18, Acrobat and Acrobat Reader DC Classic before 15.006.30243, and Acrobat and Acrobat Reader DC Continuous before 15.020.20039 on Windows and OS X allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2016-6940, CVE-2016-6941, CVE-2016-6942, CVE-2016-6943, CVE-2016-6947, CVE-2016-6948, CVE-2016-6950, CVE-2016-6951, CVE-2016-6954, CVE-2016-6955, CVE-2016-6956, CVE-2016-6959, CVE-2016-6960, CVE-2016-6966, CVE-2016-6970, CVE-2016-6972, CVE-2016-6973, CVE-2016-6974, CVE-2016-6975, CVE-2016-6976, CVE-2016-6977, CVE-2016-6978, CVE-2016-6995, CVE-2016-6996, CVE-2016-6997, CVE-2016-6998, CVE-2016-7000, CVE-2016-7001, CVE-2016-7002, CVE-2016-7003, CVE-2016-7004, CVE-2016-7005, CVE-2016-7006, CVE-2016-7007, CVE-2016-7008, CVE-2016-7009, CVE-2016-7010, CVE-2016-7011, CVE-2016-7012, CVE-2016-7013, CVE-2016-7014, CVE-2016-7015, CVE-2016-7016, CVE-2016-7017, and CVE-2016-7018.

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 confidence

Memory corruption vulnerability in Adobe Reader and Acrobat (versions before 11.0.18, 15.006.30243, or 15.020.20039) on Windows and OS X allows attackers to execute arbitrary code or cause denial of service via unspecified vectors.

MitigationUpdate Adobe Reader and Acrobat to version 11.0.18 (Classic), 15.006.30243 (DC Classic), or 15.020.20039 (DC Continuous) or later to remediate this vulnerability.

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
AcrobatApplication
Affected:<= 11.0.17
Acrobat DcApplication
Affected:<= 15.006.30201<= 15.017.20053
Acrobat Reader DcApplication
Affected:<= 15.006.30201<= 15.017.20053
ReaderApplication
Affected:<= 11.0.17

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
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 checks

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

  1. Identify installed Adobe product
    On Windows, check Start Menu for Adobe Acrobat or Adobe Reader shortcuts, or go to Control Panel > Programs and Features. On Mac OS X, open /Applications and look for Adobe Acrobat DC or Adobe Reader.
    Affected if Any Adobe Acrobat or Adobe Reader product is installed (the vulnerability applies to both)
  2. Check Adobe Reader version on Windows
    Locate AcroRd32.exe in the Reader installation folder (typically C:\Program Files\Adobe\Reader XX\Reader\AcroRd32.exe). Right-click the file, select Properties, and view the Details tab for the Product Version.
    Affected if Reader version is 11.0.17 or earlier (Classic), or 15.006.30201/15.017.20053 or earlier (DC versions)
  3. Check Adobe Acrobat version on Windows
    Locate AcroTray.exe or the main Acrobat executable in the installation folder (typically C:\Program Files\Adobe\Acrobat XX\Acrobat\AcroTray.exe). Right-click, select Properties, and view the Details tab for the Product Version.
    Affected if Acrobat version is 11.0.17 or earlier (Classic), or 15.006.30201/15.017.20053 or earlier (DC versions)
  4. Check version on Mac OS X
    Open Finder, navigate to /Applications/Adobe Reader or /Applications/Adobe Acrobat DC. Right-click the app, select Show Package Contents, then open Contents/Info.plist. Look for CFBundleShortVersionString or CFBundleVersion.
    Affected if Reader or Acrobat version is 11.0.17 or earlier (Classic), or 15.006.30201/15.017.20053 or earlier (DC versions)
  5. Compare against fixed versions
    Review the version you found. Fixed versions are: 11.0.18 (Classic track), 15.006.30243 (DC Classic), 15.020.20039 (DC Continuous). Any version below these thresholds is affected.
    Affected if Installed version is below 11.0.18 (Classic), below 15.006.30243 (DC Classic), or below 15.020.20039 (DC Continuous)

You are affected if Adobe Reader or Adobe Acrobat is installed and the version number is 11.0.17 or earlier for Classic versions, 15.006.30201 or earlier for DC Classic, or 15.017.20053 or earlier for DC Continuous.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 15.017.20053
Interim mitigation

Update Adobe Reader and Acrobat to version 11.0.18 (Classic), 15.006.30243 (DC Classic), or 15.020.20039 (DC Continuous) or later to remediate this vulnerability.

Recommended fix High confidence

Acrobat/Reader 11.x -> 11.0.18+ | DC Classic 15.006.x -> 15.006.30243+ | DC Continuous 15.x -> 15.020.20039+

  1. For Acrobat/Reader 11.x: Upgrade to version 11.0.18 or later
  2. For Acrobat/Reader DC Classic (15.006.x): Upgrade to version 15.006.30243 or later
  3. For Acrobat/Reader DC Continuous (15.x): Upgrade to version 15.020.20039 or later
  4. Verify the installed version via Help > About Adobe Acrobat/Reader
  5. Restart the application after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Acrobat 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-2016-7019 — 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-2016-7019 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