dbcve.org
AcrobatApplication · Adobe

CVE-2017-16410

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 a result of untrusted input that is used to calculate an array index; the calculation occurs in the image conversion module, when processing GIF files. The vulnerability leads to an operation that can write to a memory location that is outside of the memory addresses allocated for the data structure. The specific scenario leads to a write access to a memory location that does not belong to the relevant process address space.

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

Out-of-bounds write vulnerability in Adobe Acrobat and Reader's image conversion module when processing maliciously crafted GIF files. Untrusted input from the GIF file is used to calculate an array index, allowing the attacker to write to memory locations outside the allocated buffer. This memory corruption could potentially be exploited for arbitrary code execution.

MitigationApply the vendor-supplied security updates for Adobe Acrobat and Reader (versions 2017.012.20099 and later, 2017.011.30067 and later, 2015.006.30356 and later, or 11.0.23 and later). Prioritize systems processing untrusted PDF documents.

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. Identify installed Adobe product
    Open Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat Reader (or Acrobat) to see the exact version number displayed in the dialog box.
    Affected if The product shown is Adobe Acrobat or Adobe Acrobat Reader (any variant: Classic or DC).
  2. Determine the product variant
    Check if the installed product is Acrobat/Reader Classic or Acrobat/Reader DC. This can be determined from the product name shown in the About dialog and the install location (e.g., 'Acrobat DC' vs 'Acrobat 11.0').
    Affected if The variant is Acrobat/Reader DC or Acrobat/Reader Classic.
  3. Compare version against affected ranges
    Match your exact version number to the affected ranges: Classic (11.x): <= 11.0.22 is vulnerable; 2017 (17.x): >= 17.0 and <= 17.011.30066 is vulnerable; 2015 (15.x): >= 15.0 and <= 15.006.30355 is vulnerable; DC variants: <= 17.012.20098 or <= 15.006.30355 depending on the year track.
    Affected if Your installed version falls within any of these ranges: 11.0.22 or lower, 17.0 through 17.011.30066, 15.0 through 15.006.30355, or DC versions <= 17.012.20098 (2017) / <= 15.006.30355 (2015).
  4. Verify GIF processing capability is present
    The image conversion module that handles GIF files is built into the core product. To check if it exists, examine the product installation directory for the imaging conversion DLLs (e.g.,CoolType.dll or image conversion related files).
    Affected if Adobe Acrobat or Reader is installed with the standard image conversion components intact.

You are affected if Adobe Acrobat or Reader is installed and the version number falls within the vulnerable ranges listed above (11.0.22 or lower, 17.x up to 17.011.30066, 15.x up to 15.006.30355, or DC variants <= 17.012.20098 / <= 15.006.30355).

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 the vendor-supplied security updates for Adobe Acrobat and Reader (versions 2017.012.20099 and later, 2017.011.30067 and later, 2015.006.30356 and later, or 11.0.23 and later). Prioritize systems processing untrusted PDF documents.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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