CVE-2017-1712
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 · unedited"A vulnerability in the TLS protocol implementation of the Domino server could allow an unauthenticated, remote attacker to access sensitive information, aka a Return of Bleichenbacher's Oracle Threat (ROBOT) attack. An attacker could iteratively query a server running a vulnerable TLS stack implementation to perform cryptanalytic operations that may allow decryption of previously captured TLS sessions."
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 server contains a vulnerable TLS implementation susceptible to the Return of Bleichenbacher's Oracle Threat (ROBOT) attack. The vulnerability allows an unauthenticated remote attacker to exploit RSA encryption in TLS handshakes by iteratively querying the server and observing responses, enabling cryptanalytic decryption of previously captured TLS sessions.
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< 9.0.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 Domino server versionRun 'tell http version' from Domino server console, or check the installed product version via IBM Domino Administrator client, or examine the notes.ini file for the version stringAffected if The installed version is any release prior to 9.0.1 (versions 9.0.0, 8.5.x, and earlier)
-
Verify RSA key exchange ciphers are enabledAccess Domino server document in Domino Directory, navigate to Internet Protocols > HTTP tab, inspect the 'SSL cipher suites' or 'Cipher specs' field. Look for ciphers using RSA key exchange such as TLS_RSA_WITH_* ciphersAffected if Any RSA-based key exchange cipher suites are listed and enabled in the SSL/TLS configuration
-
Confirm TLS listener is activeFrom Domino server console, run 'show port', 'show tasks', or check if HTTP task is listening on port 443 (HTTPS) via netstat or similar utilityAffected if The Domino HTTP task is running and the server is listening on HTTPS ports (typically 443 or 4433)
-
Check TLS protocol versions enabledIn Domino server document, under Internet Protocols > HTTP, examine enabled TLS protocol versions. Check notes.ini for SSLDisableTLS10 or SSLDisableTLS11 parameters if presentAffected if TLS 1.0 or TLS 1.1 are enabled (these older protocols are more susceptible to padding oracle attacks)
-
Test server response to malformed RSA paddingUsing a TLS testing tool such as testssl.sh or SSL Labs SSL test, send a ClientKeyExchange with incorrectly padded RSA premaster secret and observe server response behaviorAffected if The server returns a valid Finished message or does not properly reject malformed RSA padding (indicating a padding oracle exists)
Your environment is affected if Domino version is below 9.0.1 AND the server has RSA key exchange cipher suites enabled AND is accessible via HTTPS, allowing an attacker to perform cryptanalytic padding oracle attacks.
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 data9.0.1
Apply the IBM Domino security update for CVE-2017-1712 to patch the TLS implementation, and consider disabling vulnerable RSA cipher suites or implementing TLS1.2 with proper padding countermeasures.
- 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-2017-1712 — 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-1712 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