CVE-2017-3043
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 · uneditedAdobe 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 collaboration functionality.
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 confidenceThis is an information disclosure vulnerability in Adobe Acrobat Reader where the collaboration functionality leaks memory addresses. The memory address leak could potentially aid attackers in bypassing address space layout randomization (ASLR) security protections, making other exploits more reliable.
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<= 11.0.19<= 15.006.30280<= 15.023.20070<= 15.006.30280<= 15.023.20070<= 11.0.19CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe product and versionOpen Adobe Acrobat/Reader, then go to Help > About to display the exact version number. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Adobe\Adobe Acrobat\[version] or HKLM\SOFTWARE\Adobe\Adobe Reader\[version] for the Version key.Affected if The displayed version falls within these ranges: Acrobat/Reader 11.0.19 or lower; Acrobat/Reader DC 15.006.30280 or lower, or 15.023.20070 or lower (verify which branch is installed).
-
Verify Adobe collaboration feature is enabledIn Adobe Acrobat/Reader, navigate to Edit > Preferences > Security (or Privacy) and look for Collaboration or Commenting settings. Alternatively, check if the Collaboration plugin ( Collab) is loaded by viewing the product plugins list.Affected if The collaboration functionality is actively enabled or loaded in the installed version.
-
Confirm product family and build branchNote the full version string including the 4-digit build number (e.g., 15.006.30280 or 15.023.20070). Adobe Reader DC has two parallel release branches with different version numbers; identify which branch is installed.Affected if The build number matches or is lower than either 15.006.30280 or 15.023.20070 (whichever branch the installation belongs to).
The system is affected if Adobe Acrobat or Reader is installed with a version at or below the affected ranges AND the collaboration feature is enabled or present.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Adobe Acrobat Reader to a version newer than 11.0.19, 15.006.30280, or 15.023.20070 (depending on the product line). For enterprise deployments, use vendor patch management to ensure all affected installations are updated.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2017-3043 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-3043 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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