dbcve.org
DominoApplication · Ibm

CVE-2015-0117

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
The LDAP Server in IBM Domino 8.5.x before 8.5.3 FP6 IF6 and 9.x before 9.0.1 FP3 IF1 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, aka SPR KLYH9SLRGM.

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

Memory corruption vulnerability in the LDAP server component of IBM Domino versions 8.5.x before 8.5.3 FP6 IF6 and 9.x before 9.0.1 FP3 IF1 allows remote unauthenticated attackers to execute arbitrary code or cause denial of service via unspecified vectors.

MitigationApply the vendor patches by upgrading IBM Domino to version 8.5.3 FP6 IF6 or 9.0.1 FP3 IF1. As an interim measure, restrict or disable LDAP server access if not required, and ensure LDAP services are not exposed to untrusted networks.

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 installed IBM Domino version
    Run 'show server' at the Domino console or check the program directory for the version file. Compare the version number to the affected ranges: 8.5.0 through 8.5.3 (before FP6 IF6) and 9.0.1 (before FP3 IF1).
    Affected if The installed version is 8.5.0, 8.5.1, 8.5.2, 8.5.3, or 9.0.1 without the indicated fix packs.
  2. Verify LDAP server task is enabled
    At the Domino console, run 'show task' or check the server configuration document in Domino Administrator. Look for 'LDAP' in the list of running tasks.
    Affected if The LDAP task is listed as running or available on the server.
  3. Confirm LDAP is configured as a listener
    Check the server's port configuration in Domino Directory under Server > Ports > Internet Ports. Verify if LDAP is assigned a TCP/IP port (default 389).
    Affected if LDAP is assigned an active TCP port and the listener is enabled.
  4. Assess LDAP network exposure
    Review firewall rules and server access restrictions. Determine if LDAP port 389 (or configured alternate) is accessible from untrusted networks.
    Affected if LDAP port is open to untrusted or public networks without access controls.

A server is affected if it runs a vulnerable Domino version (8.5.0-8.5.3 or 9.0.1 without the fix packs) AND has the LDAP server task enabled and accessible over the network.

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 vendor patches by upgrading IBM Domino to version 8.5.3 FP6 IF6 or 9.0.1 FP3 IF1. As an interim measure, restrict or disable LDAP server access if not required, and ensure LDAP services are not exposed to untrusted networks.

Recommended fix High confidence

IBM Domino 8.5.3 FP6 IF6 or later (or 9.0.1 FP3 IF1 or later)

  1. Confirm current IBM Domino version by running 'show version' or checking Domino Administrator
  2. For Domino 8.5.x: Upgrade to 8.5.3 Fix Pack 6 with Interim Fix 6 (IF6) or later
  3. For Domino 9.x: Upgrade to 9.0.1 Fix Pack 3 with Interim Fix 1 (IF1) or later
  4. Download the fix from IBM Fix Central (https://www.ibm.com/support/fixcentral/) or the vendor patch URL provided
  5. Apply the fix following IBM standard Domino patch installation procedures
  6. Restart the Domino server after applying the fix
  7. Verify the LDAP server is functioning correctly post-upgrade
Caveat Review IBM release notes for Domino 8.5.3 FP6 or 9.0.1 FP3 for any configuration or compatibility changes before upgrading

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

Fix this in Domino Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0117 — 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-0117 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