dbcve.org
AcrobatApplication · Adobe

CVE-2017-3010

CRITICAL · 9.8 CVSS v3.0 Published 2017-03-31
Fix available
A fix is available. Upgrade to after 15.020.20042 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 Reader versions 15.020.20042 and earlier, 15.006.30244 and earlier, 11.0.18 and earlier have an exploitable memory corruption vulnerability in the rendering engine. 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 · high confidence

Adobe Acrobat Reader contains a memory corruption vulnerability in its rendering engine affecting versions 15.020.20042 and earlier, 15.006.30244 and earlier, and 11.0.18 and earlier. The flaw allows attackers to achieve arbitrary code execution through specially crafted PDF documents.

MitigationUpdate Adobe Acrobat Reader to the latest patched version beyond 15.020.20042, 15.006.30244, and 11.0.18 to remediate this vulnerability.

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.0, <= 11.0.18
Acrobat DcApplication
Affected:>= 15.000.0000, <= 15.006.30244>= 15.000.0000, <= 15.020.20042
Acrobat Reader DcApplication
Affected:>= 15.000.0000, <= 15.006.30244>= 15.000.0000, <= 15.020.20042
ReaderApplication
Affected:>= 11.0.0, <= 11.0.18

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. Identify installed Adobe product
    On Windows, open Control Panel > Programs and Features and look for Adobe Acrobat or Adobe Reader entries. On macOS, check /Applications folder.
    Affected if Any Adobe Acrobat or Adobe Reader installation is present
  2. Determine the exact version number
    Open the application and go to Help > About (product name) to display the full version and build number, or run 'reg query "HKLM\SOFTWARE\Adobe\Acrobat Distiller" /v Version' on Windows.
    Affected if The version is visible and can be compared against affected ranges
  3. Compare version against affected ranges
    Match your installed version to the affected ranges: Adobe Reader/Acrobat 11.x versions 11.0.0 through 11.0.18 are vulnerable; Acrobat/Reader DC versions 15.000.0000 through 15.006.30244 are vulnerable; Acrobat/Reader DC versions 15.000.0000 through 15.020.20042 are vulnerable.
    Affected if Installed version falls within any of these three vulnerable ranges

The system is affected if Adobe Acrobat or Adobe Reader is installed and the version matches 11.0.0-11.0.18, 15.000.0000-15.006.30244, or 15.000.0000-15.020.20042.

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

Update Adobe Acrobat Reader to the latest patched version beyond 15.020.20042, 15.006.30244, and 11.0.18 to remediate this vulnerability.

Recommended fix High confidence

Adobe Acrobat/Reader 11.0.19+ or Adobe Acrobat Dc/Reader Dc 15.006.30245+ / 15.020.20043+

  1. Identify the currently installed Adobe Acrobat or Reader version from Help > About product name
  2. For Adobe Acrobat/Reader 11.x (version 11.0.0 to 11.0.18): Upgrade to version 11.0.19 or later
  3. For Adobe Acrobat Dc/Reader Dc version 15.006.30000-15.006.30244: Upgrade to version 15.006.30245 or later
  4. For Adobe Acrobat Dc/Reader Dc version 15.020.20042 and earlier: Upgrade to version 15.020.20043 or later
  5. Download the appropriate update from the official Adobe Security Bulletins page (helpx.adobe.com/security) or use the product's automatic update feature (Help > Check for Updates)
  6. After upgrading, verify the new version by checking Help > About to confirm the vulnerability is remediated
Caveat Standard security patch with no expected breaking changes; standard upgrade procedure for Adobe products

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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