CVE-2017-3009
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 15.020.20042 and earlier, 15.006.30244 and earlier, 11.0.18 and earlier have an exploitable buffer overflow vulnerability in the JPEG2000 parser. Successful exploitation could lead to information disclosure.
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 buffer overflow vulnerability in its JPEG2000 image parser. The vulnerability can be triggered when parsing specially crafted JPEG2000 images, potentially allowing an attacker to read sensitive information from the victim's system. The issue affects versions 15.020.20042 and earlier, 15.006.30244 and earlier, and 11.0.18 and earlier.
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.0, <= 11.0.18>= 15.000.0000, <= 15.006.30244>= 15.000.0000, <= 15.020.20042>= 15.000.0000, <= 15.006.30244>= 15.000.0000, <= 15.020.20042>= 11.0.0, <= 11.0.18CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 and navigate to Help > About Adobe Acrobat Reader (or similar menu item). On Windows, also check Add or Remove Programs in Control Panel. Note the exact product name displayed (Acrobat, Acrobat Reader, Acrobat DC, Reader DC, etc.).Affected if The product is Adobe Acrobat, Adobe Acrobat Reader, Adobe Reader, or their DC variants.
-
Determine installed version numberLocate the full version string shown in the About dialog (for example, 15.020.20042 or 11.0.18). Record all four numeric segments for DC products or three for classic products.Affected if A version number is displayed that can be compared against the affected ranges.
-
Compare version against affected rangesFor classic products (non-DC), check if version is >= 11.0.0 and <= 11.0.18. For DC products, check if version is >= 15.000.0000 and <= 15.006.30244, OR >= 15.000.0000 and <= 15.020.20042.Affected if The installed version falls within any of these ranges: 11.0.0-11.0.18, 15.000.0000-15.006.30244, or 15.000.0000-15.020.20042.
If Adobe Acrobat or Reader is installed with a version matching the ranges above, the environment is affected by this vulnerability.
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 dataApply the vendor-supplied security update to Adobe Acrobat Reader to obtain a version newer than those affected. Alternatively, disable JavaScript in Acrobat Reader settings to reduce the attack surface.
- 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-3009 — 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-3009 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