dbcve.org
AcrobatApplication · Adobe

CVE-2017-3053

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 image conversion engine, related to parsing of the APP13 segment in JPEG files.

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 address leak vulnerability in its image conversion engine when parsing JPEG files containing a specially crafted APP13 segment. When a user opens a malicious PDF containing such a JPEG, the application leaks memory addresses which could potentially be leveraged to bypass memory protection mechanisms in coordinated attacks.

MitigationUpdate Adobe Acrobat Reader to a version newer than 11.0.19, 15.006.30280, or 15.023.20070 as appropriate for the installed product line.

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, Reader, or Acrobat DC. Go to Help > About [Product Name] to see the exact product name and version number.
    Affected if The product is Adobe Acrobat, Adobe Acrobat DC, Adobe Acrobat Reader DC, or Adobe Reader.
  2. Check Adobe Acrobat version
    If using Adobe Acrobat (non-DC), verify the version number against 11.0.19. Open Help > About Adobe Acrobat and note the version shown (e.g., 11.0.19 or lower).
    Affected if The installed version is 11.0.19 or any earlier version.
  3. Check Adobe Acrobat DC version
    If using Adobe Acrobat DC, verify the version against both 15.006.30280 and 15.023.20070. Open Help > About Adobe Acrobat DC and note the version and build number.
    Affected if The installed version is 15.006.30280 or lower, OR 15.023.20070 or lower.
  4. Check Adobe Acrobat Reader DC version
    If using Adobe Acrobat Reader DC, verify the version against both 15.006.30280 and 15.023.20070. Open Help > About Adobe Acrobat Reader DC and note the version and build number.
    Affected if The installed version is 15.006.30280 or lower, OR 15.023.20070 or lower.
  5. Check Adobe Reader version
    If using Adobe Reader (non-DC), verify the version number against 11.0.19. Open Help > About Adobe Reader and note the version shown.
    Affected if The installed version is 11.0.19 or any earlier version.
  6. Verify PDF parsing is the trigger condition
    This vulnerability is triggered when the application parses a PDF file containing a JPEG image with a specially crafted APP13 segment. The image conversion engine processes these files automatically when opened in the application.
    Affected if The installed product version falls within the affected ranges AND the application is used to open PDF files containing JPEG images.

A user is affected if their installed Adobe product version matches or is lower than the affected version ranges for their specific product line (11.0.19 for Acrobat/Reader, or 15.006.30280/15.023.20070 for DC variants).

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 newer than 11.0.19, 15.006.30280, or 15.023.20070 as appropriate for the installed product line.

Fix this in Acrobat Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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