CVE-2016-0304
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 · uneditedThe Java Console in IBM Domino 8.5.x before 8.5.3 FP6 IF13 and 9.x before 9.0.1 FP6, when a certain unsupported configuration involving UNC share pathnames is used, allows remote attackers to bypass authentication and possibly execute arbitrary code via unspecified vectors, aka SPR KLYHA7MM3J. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-0920.
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 confidenceIBM Domino Java Console contains an authentication bypass vulnerability when an unsupported configuration involving UNC share pathnames is used. Remote attackers can bypass authentication and potentially execute arbitrary code. This is an incomplete fix for the older CVE-2011-0920.
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.3= 8.5.3.1= 8.5.3.2= 8.5.3.3= 8.5.3.4= 8.5.3.5= 8.5.3.6= 8.5.2= 8.5.2.1= 8.5.2.2= 8.5.2.3= 8.5.2.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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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 IBM Domino versionRun 'show server' command in Domino console or check server document in Domino Directory for the Domino server version numberAffected if Installed version is 8.5.2.x or 8.5.3.x (specifically 8.5.2, 8.5.2.1, 8.5.2.2, 8.5.2.3, 8.5.2.4, 8.5.3, 8.5.3.1, 8.5.3.2, 8.5.3.3, 8.5.3.4, 8.5.3.5, or 8.5.3.6)
-
Verify Java Console is enabledCheck server document in Domino Directory under Server\Servers\ServerName\Ports\Internet Ports\Directory and Web Administration ports; look for Java Console port (usually port 8009 or similar) enabled for HTTP or ensure Java Controller is runningAffected if Java Console is enabled and accessible over network
-
Check for UNC share pathname configurationReview server document and notes.ini for any UNC paths (\\server\share) configured for Domino data directory, programs directory, or Java console-related paths; inspect Domino data directory path settings in server documentAffected if Server uses UNC share pathnames (\\server\sharename) for Domino directories or Java Console configuration
-
Confirm Java Controller authentication settingsExamine notes.ini for 'JavaControllerAccess' and 'JavaConsolePort' settings; verify if unauthenticated access is permitted to the Java ConsoleAffected if Java Console allows unauthenticated or insufficiently authenticated access
User is affected if running a vulnerable 8.5.2.x or 8.5.3.x version of IBM Domino with Java Console enabled and the server configured to use UNC share pathnames for directories or Java Console settings.
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 patches 8.5.3 FP6 IF13 or 9.0.1 FP6 depending on version, and avoid using the unsupported UNC share pathname configuration.
- 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-0304 — 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-0304 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