AcrobatApplication · Adobe

CVE-2017-3045

MEDIUM · 5.5 CVSS v3.0 Published 2017-04-12
Fix available
A fix is available. Upgrade to after 15.023.20070 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Adobe Acrobat Reader versions 11.0.19 and earlier, 15.006.30280 and earlier, 15.023.20070 and earlier have a memory address leak vulnerability in the JPEG 2000 parser, related to the palette box.

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

Adobe Acrobat Reader contains a memory address information disclosure vulnerability in its JPEG 2000 parser when processing palette box data. The flaw leaks memory addresses that could assist an attacker in bypassing ASLR memory protections, potentially enabling more reliable exploitation of other vulnerabilities. The vulnerability is triggered when a user opens a specially crafted PDF file containing a malicious JPEG 2000 image.

MitigationUpdate Adobe Acrobat Reader to a version later than 11.0.19, 15.006.30280, or 15.023.20070 as applicable to the installed product line. Organizations should deploy updates via their patch management systems and verify completion across endpoints.

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.19
Acrobat DcApplication
Affected:<= 15.006.30280<= 15.023.20070
Acrobat Reader DcApplication
Affected:<= 15.006.30280<= 15.023.20070
ReaderApplication
Affected:<= 11.0.19

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/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 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 (or on Windows, check Programs and Features for the installed application name and version)
    Affected if The installed product is Adobe Acrobat, Adobe Acrobat Reader DC, Adobe Reader, or Adobe Acrobat DC Classic or Continuous variant
  2. Determine exact version number
    In the application, go to Help > About Adobe [Product Name] to display the exact version string (for example: 11.0.19, 15.006.30280, or 15.023.20070)
    Affected if Version cannot be determined or is older than the installed product baseline
  3. Compare version against affected ranges
    Match your installed version to the affected version list: Adobe Acrobat/Reader 11.x versions up to and including 11.0.19; Acrobat/Reader DC versions up to and including 15.006.30280 OR up to and including 15.023.20070 (note: there are two separate version tracks - Classic and Continuous)
    Affected if Your installed version falls within any of these ranges: 11.x <= 11.0.19, DC Classic <= 15.006.30280, or DC Continuous <= 15.023.20070
  4. Confirm JPEG 2000 parsing is reachable
    This vulnerability is triggered when processing a malicious JPEG 2000 image embedded in a PDF. No special configuration check is needed - the flaw exists in the JPEG 2000 parser component regardless of settings
    Affected if Any PDF with a crafted JPEG 2000 image can trigger the parser during normal document viewing

If the installed Adobe Acrobat/Reader version is 11.0.19 or earlier, 15.006.30280 or earlier (Classic track), or 15.023.20070 or earlier (Continuous track), the environment is affected by this vulnerability.

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

Update Adobe Acrobat Reader to a version later than 11.0.19, 15.006.30280, or 15.023.20070 as applicable to the installed product line. Organizations should deploy updates via their patch management systems and verify completion across endpoints.

Fix this in Acrobat Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-3045 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