CVE-2017-3046
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 JPEG 2000 parser, related to contiguous code-stream parsing.
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 confidenceAdobe Acrobat Reader contains a memory address leak vulnerability in its JPEG 2000 parser when parsing contiguous code-streams. This information disclosure flaw could allow an attacker to obtain sensitive memory layout information, potentially aiding in the exploitation of other vulnerabilities through ASLR bypass.
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 productOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat Reader (or similar menu item) to see which specific product is installed. Look for product name such as Adobe Acrobat, Adobe Acrobat Reader, Adobe Acrobat DC, or Adobe Reader DC.Affected if The installed product is any of Acrobat, Acrobat Reader, Acrobat DC, or Reader DC.
-
Locate the version numberIn the About dialog window, locate the version number displayed (for example, it may show a number like 11.0.19 or 15.006.30280). Note the full version string exactly as shown.Affected if A version number is displayed in the About dialog.
-
Determine the product lineageCheck if the product is DC (Document Cloud) variant or classic version. Classic versions are typically labeled as Adobe Acrobat or Adobe Reader. DC variants will have "DC" in the product name.Affected if The product is either a DC variant (Acrobat DC or Reader DC) or a classic version (Acrobat or Reader).
-
Compare classic version against affected rangeIf you have Adobe Acrobat or Adobe Reader (classic), compare the installed version against 11.0.19. If the version number is 11.0.19 or lower, the installation is within the affected range.Affected if The version is 11.0.19 or lower for classic Adobe Acrobat or Adobe Reader.
-
Compare DC version against affected rangesIf you have Adobe Acrobat DC or Adobe Reader DC, compare the installed version against both 15.006.30280 and 15.023.20070. If the version is either 15.006.30280 or lower, OR between 15.006.30281 and 15.023.20070 inclusive, the installation is affected.Affected if The DC version is 15.006.30280 or lower, or falls between 15.006.30281 and 15.023.20070 inclusive.
You are affected if your installed Adobe Acrobat or Reader version is at or below 11.0.19 for classic versions, or at or below 15.006.30280 or within the 15.006.30281 to 15.023.20070 range for DC versions.
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 as applicable to the installation.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3046 — 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-3046 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