CVE-2016-0301
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 · uneditedHeap-based buffer overflow in the KeyView PDF filter in IBM Domino 8.5.x before 8.5.3 FP6 IF13 and 9.x before 9.0.1 FP6 allows remote attackers to execute arbitrary code via a crafted PDF document, a different vulnerability than CVE-2016-0277, CVE-2016-0278, and CVE-2016-0279.
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 confidenceHeap-based buffer overflow vulnerability in IBM Domino's KeyView PDF filter allows remote attackers to execute arbitrary code via specially crafted PDF documents. Affects Domino 8.5.x before 8.5.3 FP6 IF13 and 9.x before 9.0.1 FP6.
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= 8.5.0= 9.0.1= 9.0.1.1= 9.0.1.2= 9.0.1.3= 9.0.1.4= 9.0.1.5= 8.5.3= 8.5.3.1= 8.5.3.2= 8.5.3.3= 8.5.3.4CVSS 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.
-
Determine IBM Domino server versionAccess the Domino server console or check the server version by running 'tell server version' or inspecting the server's program files for version information. Compare the installed version against the affected ranges: 8.5.x before 8.5.3 FP6 IF13 and 9.x before 9.0.1 FP6.Affected if The installed version is 8.5.0, 8.5.3 through 8.5.3.4, 9.0.1 through 9.0.1.5, or any version below 8.5.3 FP6 IF13 (for 8.5.x) or below 9.0.1 FP6 (for 9.x).
-
Verify KeyView PDF filter is in useConfirm whether the Domino server processes PDF attachments through the KeyView filter. This is typically enabled by default for Domino servers that handle PDF rendering or conversion. Check server configuration or document processing settings for KeyView PDF filter activity.Affected if The KeyView PDF filter is enabled and the server processes PDF attachments, which is the default configuration for affected Domino versions.
-
Confirm fix pack levelCheck the installed fix pack version on the Domino server. Look for FP6 IF13 for 8.5.x branches or FP6 for 9.0.1 branches. This information is visible via the Domino console command or in the program directory version details.Affected if The server is running a version without the required fix pack: 8.5.3 FP6 IF13 or later for 8.5.x, or 9.0.1 FP6 or later for 9.x.
The environment is affected if the Domino server version is 8.5.x before 8.5.3 FP6 IF13 or 9.x before 9.0.1 FP6 AND the KeyView PDF filter is enabled, which is the default configuration for processing PDF attachments.
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 IBM Domino fix packs 8.5.3 FP6 IF13 or 9.0.1 FP6 to address the heap overflow in the KeyView PDF filter component.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0301 — 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-2016-0301 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