CVE-2019-16464
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 , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
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 a use-after-free vulnerability in Adobe Acrobat and Reader that allows attackers to access memory after it has been freed, potentially leading to arbitrary code execution. The vulnerability affects multiple version families (2015, 2017, and 2019) across both major 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>= 15.006.30060, < 15.006.30508>= 15.008.20082, < 19.021.20058>= 17.011.30059, < 17.011.30156>= 15.006.30060, < 15.006.30508>= 15.008.20082, < 19.021.20058>= 17.011.30059, < 17.011.30156CVSS 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.1/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.
-
Check if Adobe Acrobat DC or Reader DC is installedOpen Windows Control Panel > Programs and Features, or macOS Applications folder. Look for Adobe Acrobat DC or Adobe Acrobat Reader DC in the installed software list.Affected if Either Adobe Acrobat DC or Adobe Acrobat Reader DC is present on the system
-
Obtain the exact version number of the installed productOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat DC (or Reader DC). The version number will display in the format like 15.x.xxxxx or 17.x.xxxxx or 19.x.xxxxx.Affected if The version shown does not match a patched version (see version ranges in CVE description)
-
Compare installed version against affected version rangesMatch your version number against these vulnerable ranges: 15.006.30060 through 15.006.30508; 15.008.20082 through 19.021.20058; 17.011.30059 through 17.011.30156.Affected if The installed version falls within any of these ranges and has not been updated to the patched versions (15.006.30508 or higher, 19.021.20058 or higher, 17.011.30156 or higher)
You are affected if Adobe Acrobat DC or Reader DC is installed and the version number falls within any of the three vulnerable version ranges specified in the CVE.
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 · scoped15.006.3050817.011.3015619.021.20058
Apply the vendor-supplied security updates for Adobe Acrobat and Reader to the patched versions. In enterprise environments, deploy updates via software distribution mechanisms and verify completion across all affected systems.
Acrobat DC/Reader DC 2019 version 19.021.20058 or later (or corresponding fixed versions for 2017 and 2015 tracks: 17.011.30156 and 15.006.30508 respectively)
- 1. Determine your current Adobe Acrobat or Acrobat Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. Identify which version track your installation belongs to (2015/15.x, 2017/17.x, or 2019/19.x).
- 3. For Acrobat/Reader 2015 (15.x track): Upgrade to version 15.006.30508 or later.
- 4. For Acrobat/Reader 2017 (17.x track): Upgrade to version 17.011.30156 or later.
- 5. For Acrobat/Reader 2019 (19.x track): Upgrade to version 19.021.20058 or later.
- 6. Download the appropriate updated version from the official Adobe website at get.adobe.com/reader or get.adobe.com/acrobat.
- 7. Close all Adobe applications before running the installer.
- 8. Install the update and restart the application.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16464 — 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-2019-16464 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