AcrobatApplication · Adobe

CVE-2017-3034

HIGH · 7.8 CVSS v3.0 Published 2017-04-12
Fix available
A fix is available. Upgrade to after 15.023.20070 or later.
See remediation →
81/100
Remediation priority · High
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 an exploitable integer overflow vulnerability in the XML Forms Architecture (XFA) engine, related to layout functionality. 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 · moderate confidence

This is an integer overflow vulnerability in Adobe Acrobat Reader's XML Forms Architecture (XFA) engine, specifically within layout processing functionality. The integer overflow can corrupt memory allocation boundaries, potentially allowing an attacker to overwrite adjacent memory and achieve arbitrary code execution through a specially crafted PDF file.

MitigationUpdate Adobe Acrobat Reader to versions later than 11.0.19, 15.006.30280, or 15.023.20070 respectively. As a workaround, avoid opening untrusted or unexpected 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.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
High
Availability
High

CVSS:3.0/AV:L/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 the installed Adobe product
    Open Adobe Acrobat or Reader and go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). Alternatively, check the installed programs list in Windows Control Panel or the Applications folder on macOS.
    Affected if The system has Adobe Acrobat, Adobe Acrobat Reader Dc, or Adobe Reader installed
  2. Determine the exact version number
    In the About dialog, note the exact version string (for example, 11.0.19 or 15.006.30280). On Windows, you can also right-click the executable in Program Files and view Properties > Details for the File Version.
    Affected if The version number matches one of the affected ranges: 11.0.19 or lower, 15.006.30280 or lower, or 15.023.20070 or lower
  3. Verify XFA forms functionality is enabled
    In Adobe Reader/Acrobat, go to Edit > Preferences > Forms and check if 'Automatically calculate field values' is enabled, or check if the PDF contains XFA-based forms. XFA (XML Forms Architecture) is a feature used for dynamic forms in PDFs.
    Affected if XFA-based forms are present or XFA processing is enabled - the vulnerability only triggers when parsing XFA layout in a specially crafted PDF
  4. Confirm PDF handling behavior
    Try opening a standard PDF to verify the application runs normally. The vulnerability is triggered specifically by malicious PDF files using XFA elements.
    Affected if The user opens untrusted or unexpected PDF files that may contain XFA-based form content

A user is affected if they have Adobe Acrobat, Acrobat Reader Dc, or Adobe Reader installed at version 11.0.19 or lower, or version 15.006.30280 or lower (Classic), or version 15.023.20070 or lower (Continuous), and they open specially crafted PDF files with XFA form content.

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 versions later than 11.0.19, 15.006.30280, or 15.023.20070 respectively. As a workaround, avoid opening untrusted or unexpected 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-3034 — 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-3034 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