dbcve.org
DominoApplication · Ibm

CVE-2015-0134

HIGH · 10.0 CVSS v2.0 Published 2015-04-06
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Buffer overflow in the SSLv2 implementation in IBM Domino 8.5.x before 8.5.1 FP5 IF3, 8.5.2 before FP4 IF3, 8.5.3 before FP6 IF6, 9.0 before IF7, and 9.0.1 before FP2 IF3 allows remote attackers to execute arbitrary code via unspecified vectors.

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 confidence

Buffer overflow vulnerability in IBM Domino's SSLv2 implementation allows remote attackers to execute arbitrary code via unspecified vectors. The flaw affects multiple 8.5.x and 9.0.x versions before specified fix pack interim fix thresholds. CVSS 10 indicates network-exploitable, no-authentication-required critical remote code execution.

MitigationApply the specified IBM Domino interim fixes (IF3 for 8.5.1 FP5, IF3 for 8.5.2 FP4, IF6 for 8.5.3 FP6, IF7 for 9.0, IF3 for 9.0.1 FP2) or upgrade to fixed versions. Consider disabling SSLv2 as a defense-in-depth measure if SSLv2 is not required.

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
DominoApplication
Affected:= 8.5.0= 8.5.1= 8.5.2= 8.5.3= 9.0.1

CVSS 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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Domino version
    Run 'show version' at the Domino server console or inspect the program directory for version files. On Windows, check the 'IBM Domino' entry in Add/Remove Programs. On Linux/Unix, check the 'installp -l' output or the lsmprod command.
    Affected if The installed version matches 8.5.0, 8.5.1, 8.5.2, 8.5.3, or 9.0.1 (or falls below the fixed fix pack levels)
  2. Determine if SSLv2 is enabled in Domino
    Inspect the Domino server's notes.ini file for the 'SSL2=' parameter or check the SSL settings in the Domino Directory under Server Documents, Security tab. Look for SSL protocol settings that explicitly enable SSLv2.
    Affected if SSLv2 is enabled on the Domino server (SSL2=1 or similar configuration allowing SSLv2 connections)
  3. Check SSL port configuration
    Review Server Document in Domino Directory, Ports tab, and verify which SSL ports are listening. Use 'show port SSL' at the server console to list active SSL ports and their protocol bindings.
    Affected if The server accepts SSLv2 connections on any SSL port (typically port 636 for LDAP, 443 for HTTP, 993 for IMAP, 995 for POP3)

You are affected if your IBM Domino version is 8.5.0 through 9.0.1 (or below the fixed fix pack thresholds) AND SSLv2 protocol is enabled on the server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www-01.ibm.com →
Interim mitigation

Apply the specified IBM Domino interim fixes (IF3 for 8.5.1 FP5, IF3 for 8.5.2 FP4, IF6 for 8.5.3 FP6, IF7 for 9.0, IF3 for 9.0.1 FP2) or upgrade to fixed versions. Consider disabling SSLv2 as a defense-in-depth measure if SSLv2 is not required.

Recommended fix High confidence

IBM Domino 9.0.1 FP2 IF3 or later (or the appropriate Fix Pack + IF for the 8.5.x line)

  1. Identify the currently installed IBM Domino version and Fix Pack level using the Domino Administrator client or by checking the version via command line
  2. Navigate to IBM Fix Central (fixcentral.ibm.com) or the vendor support page referenced (swg21700029)
  3. For Domino 8.5.0 or 8.5.1: Apply Fix Pack 5 (FP5) and then Interim Fix 3 (IF3)
  4. For Domino 8.5.2: Apply Fix Pack 4 (FP4) and then Interim Fix 3 (IF3)
  5. For Domino 8.5.3: Apply Fix Pack 6 (FP6) and then Interim Fix 6 (IF6)
  6. Alternatively, upgrade to Domino 9.0.1 Fix Pack 2 with Interim Fix 3 (FP2 IF3) or later
  7. After applying the patch, restart the Domino server to ensure the SSLv2 fix takes effect
  8. Verify the fix by checking the version information and confirming SSLv2 is disabled or the patch is applied
Caveat Applying Fix Packs and IFs may require server downtime; test in a non-production environment first; review IBM release notes for any compatibility concerns with custom templates or integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Domino Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,140
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,024.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0134 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0134 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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