CVE-2019-7819
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 Reader versions 2019.010.20098 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
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 confidenceOut-of-bounds read vulnerability in Adobe Acrobat Reader versions 2019.010.20098 and earlier allows disclosure of sensitive memory beyond allocated buffers. This information leak can enable attackers to bypass ASLR mitigation by revealing memory addresses. Exploitation requires user interaction via opening a malicious file.
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.000.00000, <= 15.006.30482>= 17.000.00000, <= 17.011.30127>= 19.000.00000, <= 19.010.20098>= 15.000.00000, <= 15.006.30482>= 17.000.00000, <= 17.011.30127>= 19.000.00000, <= 19.010.20098CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Adobe Acrobat Reader DC or Adobe Acrobat DC is installedOn Windows, check for the presence of Adobe Acrobat Reader DC or Adobe Acrobat DC in the installed programs list (Control Panel > Programs and Features) or use command: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Adobe*Acrobat*'}Affected if Either Adobe Acrobat Reader DC or Adobe Acrobat DC is present on the system
-
Determine the installed version numberIn Windows Programs and Features, locate the Version column for the Adobe product. Alternatively, right-click the Adobe Acrobat or Reader executable in Program Files and view Properties > Details to find the Product VersionAffected if The version cannot be determined or is not visible in the properties
-
Compare installed version against affected rangesCheck if the installed version falls within any of these ranges: 15.000.00000 to 15.006.30482, 17.000.00000 to 17.011.30127, or 19.000.00000 to 19.010.20098. Version 19.010.20098 and earlier in the 19.x line is affectedAffected if The installed version number is greater than 15.006.30482 but less than 17.000.00000, OR greater than 17.011.30127 but less than 19.000.00000, OR falls within 19.000.00000 to 19.010.20098
The environment is affected if Adobe Acrobat Reader DC or Adobe Acrobat DC is installed with a version matching any of the three vulnerable ranges (15.x up to 15.006.30482, 17.x up to 17.011.30127, or 19.x up to 19.010.20098).
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 · scopedUpdate Adobe Acrobat Reader to a version later than 2019.010.20098. Additionally, educate users to avoid opening untrusted PDF files and consider email gateway scanning to block malicious attachments.
Adobe Acrobat DC / Reader DC 2019.012.20035 or later (or latest 2020.x version)
- 1. Close all Adobe Acrobat or Acrobat Reader instances that are currently running
- 2. Visit the official Adobe download page at https://get.adobe.com/reader/ or https://get.adobe.com/acrobat/
- 3. Download the latest version of Adobe Acrobat DC or Acrobat Reader DC for your platform (Windows or macOS)
- 4. Run the installer and follow the on-screen prompts to complete the installation
- 5. After installation, verify the version by going to Help > About Adobe Acrobat/Reader and confirm the version number is higher than 19.010.20098
- 6. Re-open any previously closed Adobe applications
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7819 — 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-7819 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