dbcve.org
Acrobat DcApplication · Adobe

CVE-2019-7832

CRITICAL · 9.8 CVSS v3.0 Published 2019-05-22
Fix available
A fix is available. Upgrade to after 19.010.20100 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 Acrobat and Reader versions , 2019.012.20035 and earlier, 2019.012.20035 and earlier, 2017.011.30142 and earlier, 2017.011.30143 and earlier, 2017.011.30142 and earlier, 2015.006.30497 and earlier, and 2015.006.30498 and earlier have a heap overflow 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 confidence

Heap overflow vulnerability in Adobe Acrobat and Reader allows arbitrary code execution. The vulnerability affects multiple versions (2015, 2017, 2019) across both Windows and Mac platforms. Exploitation likely involves specially crafted PDF files that trigger the heap overflow when opened.

MitigationUpdate Adobe Acrobat and Reader to the latest patched version provided by Adobe. Until patched, exercise caution with untrusted PDF files and consider disabling JavaScript execution in Acrobat settings.

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.30495>= 15.008.20082, <= 19.010.20100>= 17.011.30056, <= 17.011.30140
Acrobat Reader DcApplication
Affected:>= 15.006.30060, <= 15.006.30493>= 15.008.20082, <= 19.010.20099>= 17.011.30059, <= 17.011.30138

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. Confirm Adobe Acrobat or Reader DC is installed
    On Windows, check Program Files for 'Adobe\Acrobat DC' or 'Adobe\Acrobat Reader DC' folders. On Mac, check /Applications for 'Adobe Acrobat DC' or 'Adobe Acrobat Reader DC'.
    Affected if Either Adobe Acrobat DC or Adobe Acrobat Reader DC is present on the system
  2. Locate the main executable file
    Navigate to the installation directory. Typical paths: Windows: C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe or C:\Program Files\Adobe\Acrobat Reader DC\Reader\Acrobat.exe. Mac: /Applications/Adobe Acrobat DC/Adobe Acrobat DC.app or /Applications/Adobe Acrobat Reader DC.app
    Affected if The executable exists at the expected path, indicating the application is installed
  3. Retrieve the installed version number
    Right-click the executable, select Properties, then the Details tab to view the File Version. Alternatively, open the application, go to Help > About Adobe Acrobat (or Reader) to display the version.
    Affected if A version number is displayed in the format such as 15.x.x.x, 17.x.x.x, or 19.x.x.x
  4. Compare version against affected ranges
    Match your installed version number against the following vulnerable ranges: 15.006.30060 to 15.006.30495, 15.008.20082 to 19.010.20100, or 17.011.30056 to 17.011.30140 for Acrobat DC. For Reader DC: 15.006.30060 to 15.006.30493, 15.008.20082 to 19.010.20099, or 17.011.30059 to 17.011.30138.
    Affected if The installed version falls within any of the listed vulnerable version ranges

The system is affected if Adobe Acrobat DC or Reader DC is installed and the version number matches any of the vulnerable ranges: 15.006.30060-15.006.30495, 15.008.20082-19.010.20100 (Acrobat), or 15.008.20082-19.010.20099 (Reader), or 17.011.30056-17.011.30140 (Acrobat), or 17.011.30059-17.011.30138 (Reader).

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 19.010.20100
Interim mitigation

Update Adobe Acrobat and Reader to the latest patched version provided by Adobe. Until patched, exercise caution with untrusted PDF files and consider disabling JavaScript execution in Acrobat settings.

Recommended fix Moderate confidence

Adobe Acrobat DC/Reader DC 2019.012.20036 or later (or latest 2020/2021 release)

  1. Verify current Adobe Acrobat or Adobe Acrobat Reader DC version by opening the application, selecting Help > About Adobe Acrobat Reader/Acrobat
  2. Download the latest version of Adobe Acrobat DC or Adobe Acrobat Reader DC from the official Adobe website at https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
  3. Close all Adobe applications and any web browsers that may have PDF plugins enabled
  4. Run the downloaded installer and follow the prompts to complete the installation
  5. After installation, verify the version has been updated to a version newer than the affected releases (2019.012.20036 or later for 2019 track, 2017.011.30143 or later for 2017 track, 2015.006.30498 or later for 2015 track)
Caveat Adobe updates may include new features or interface changes; ensure compatibility with any PDF-dependent workflows or plugins before deployment in production environments

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

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-7832 — 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-2019-7832 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