CVE-2017-3011
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 an exploitable integer overflow vulnerability in the CCITT fax PDF filter. 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 · high confidenceAdobe Acrobat Reader contains an integer overflow vulnerability in the CCITT fax PDF filter. Successful exploitation allows arbitrary code execution. Affected versions include 11.0.19 and earlier, 15.006.30280 and earlier, and 15.023.20070 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.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe productCheck the application menu: Help > About Adobe Acrobat Reader (or Acrobat). The version number appears in the dialog title or the first line of text.Affected if The product name is Adobe Acrobat, Adobe Acrobat Reader, Adobe Acrobat Dc, or Adobe Acrobat Reader Dc
-
Extract the full version numberNote the version number shown (for example, 11.0.19 or 15.006.30280). On Windows, you can also right-click the executable (AcroRd32.exe or AcroRd64.exe) in the program files folder and view Properties > Details > File Version.Affected if A four-part version number like X.X.X.X is displayed
-
Compare against affected version rangesMatch your version to the affected ranges: for version 11.x compare against <=11.0.19; for version 15.x compare against both <=15.006.30280 and <=15.023.20070 (the product had two distinct version tracks).Affected if Your version is 11.0.19 or earlier, OR 15.006.30280 or earlier, OR 15.023.20070 or earlier
-
Confirm CCITT fax processing is possibleThe CCITT fax filter is a built-in component that processes Group 3/4 TIFF compressed data in PDF files. No explicit enablement check is needed as this is core PDF rendering functionality.Affected if Adobe Reader or Acrobat processes PDF documents, which may contain CCITT-compressed image data automatically handled by the filter
You are affected if Adobe Acrobat or Adobe Reader is installed with a version number at or below 11.0.19, 15.006.30280, or 15.023.20070 (depending on your product line and version track).
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 dataUpgrade Adobe Acrobat Reader to the latest version beyond the affected releases (11.0.19, 15.006.30280, 15.023.20070) to patch the integer overflow in the CCITT fax filter.
- 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-3011 — 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-3011 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