dbcve.org
AcrobatApplication · Adobe

CVE-2017-16374

HIGH · 8.8 CVSS v3.0 Published 2017-12-09
Fix available
A fix is available. Upgrade to after 17.012.20098 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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
An issue was discovered in Adobe Acrobat and Reader: 2017.012.20098 and earlier versions, 2017.011.30066 and earlier versions, 2015.006.30355 and earlier versions, and 11.0.22 and earlier versions. The vulnerability is caused by a buffer over-read in the JPEG 2000 module. An invalid JPEG 2000 input code stream leads to a computation where the pointer arithmetic results in a location outside valid memory locations belonging to the buffer. An attack can be used to obtain sensitive information, such as object heap addresses, etc.

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

Buffer over-read vulnerability in Adobe Acrobat and Reader's JPEG 2000 image processing module. Processing a specially crafted JPEG 2000 file with invalid input causes pointer arithmetic to read beyond buffer boundaries, allowing attackers to obtain sensitive information such as heap addresses.

MitigationApply Adobe security updates/patches for Acrobat and Reader to the fixed versions (2017.012.20099 and later, 2017.011.30067 and later, 2015.006.30356 and later, 11.0.23 and later).

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.22>= 17.0, <= 17.011.30066
Acrobat DcApplication
Affected:>= -, <= 17.012.20098>= 15.0, <= 15.006.30355
Acrobat ReaderApplication
Affected:<= 11.0.22>= 17.0, <= 17.011.30066
Acrobat Reader DcApplication
Affected:>= -, <= 17.012.20098>= 15.0, <= 15.006.30355

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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. Verify Adobe Acrobat or Reader is installed
    Check for the presence of Adobe Acrobat or Adobe Reader in the system. On Windows, look in C:\Program Files\Adobe or C:\Program Files (x86)\Adobe, or check Add/Remove Programs. On macOS, check /Applications for Adobe Acrobat or Adobe Reader.
    Affected if Adobe Acrobat or Adobe Reader is installed on the system
  2. Determine the installed version number
    Open Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat (or About Adobe Reader) to display the exact version number and description. Alternatively, check the application properties in the Windows registry under HKLM\SOFTWARE\Adobe\Adobe Acrobat or HKLM\SOFTWARE\Adobe\Adobe Reader.
    Affected if A version number is displayed that can be compared against affected ranges
  3. Compare version against affected ranges for standard Acrobat/Reader
    For Adobe Acrobat or Reader (non-DC), check if the version is <= 11.0.22 OR falls between 17.0 and 17.011.30066 inclusive. These versions are affected by the buffer over-read.
    Affected if Version is 11.0.22 or lower, OR between 17.0 and 17.011.30066 inclusive
  4. Compare version against affected ranges for Acrobat DC/Reader DC
    For Adobe Acrobat DC or Adobe Reader DC, check if the version is between 15.0 and 15.006.30355 inclusive, OR between 17.0 and 17.012.20098 inclusive. These versions are affected.
    Affected if Version is between 15.0 and 15.006.30355 inclusive, OR between 17.0 and 17.012.20098 inclusive

If Adobe Acrobat or Reader is installed and the version falls within any of the affected ranges (11.0.22 or lower, 17.0-17.011.30066, 15.0-15.006.30355, or 17.0-17.012.20098), the environment is vulnerable to CVE-2017-16374 when processing JPEG 2000 image files.

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

Apply Adobe security updates/patches for Acrobat and Reader to the fixed versions (2017.012.20099 and later, 2017.011.30067 and later, 2015.006.30356 and later, 11.0.23 and later).

Fix this in Acrobat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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