dbcve.org
DominoApplication · Ibm

CVE-2015-1902

HIGH · 10.0 CVSS v2.0 Published 2015-05-20
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
Stack-based buffer overflow in IBM Domino 8.5 before 8.5.3 FP6 IF7 and 9.0 before 9.0.1 FP3 IF3 allows remote attackers to execute arbitrary code via a crafted BMP image, aka SPR KLYH9TSMLA.

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

A stack-based buffer overflow vulnerability exists in IBM Domino server versions 8.5 before 8.5.3 FP6 IF7 and 9.0 before 9.0.1 FP3 IF3. The flaw resides in the image processing component that handles BMP files. Remote attackers can exploit this by sending a specially crafted BMP image to the server, causing a buffer overflow that allows execution of arbitrary code with the privileges of the Domino service.

MitigationUpgrade IBM Domino to version 8.5.3 FP6 IF7, 9.0.1 FP3 IF3, or later. Additionally, restrict or disable BMP image processing capabilities in Domino if not required, and implement network-level controls to limit exposure to untrusted BMP files.

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 the command 'tell server version' from the Domino server console, or check the version via the IBM Domino Administrator client under Server > Status, or inspect the notes.ini file for the version string.
    Affected if The installed version is 8.5.0, 8.5.1, 8.5.2, 8.5.3, or 9.0.1 (before the respective fixed IF releases)
  2. Verify Domino HTTP task is running
    From the Domino server console, run 'show tasks' or 'tell http show config' to confirm the HTTP task is active and accepting requests.
    Affected if The HTTP task is running and the server is accessible over HTTP/HTTPS, enabling remote attackers to send malicious BMP files
  3. Confirm BMP image processing is accessible
    Check if the Domino server has the ability to process or display BMP images by attempting to upload a BMP file through any Domino web application, or review the Domino document handling configuration for supported image types.
    Affected if BMP image processing is enabled or available through any Domino web application, form, or attachment handling mechanism
  4. Check for untrusted BMP file handling
    Review Domino web applications for any functionality that accepts image uploads, displays attached images, or processes image thumbnails, particularly in areas accessible to anonymous or untrusted users.
    Affected if Any web application or component accepts BMP files from untrusted sources without validation

The environment is affected if the installed Domino version matches 8.5.0 through 9.0.1 before the fixed interim fix levels AND the server exposes BMP image processing functionality to potential attackers.

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

Upgrade IBM Domino to version 8.5.3 FP6 IF7, 9.0.1 FP3 IF3, or later. Additionally, restrict or disable BMP image processing capabilities in Domino if not required, and implement network-level controls to limit exposure to untrusted BMP files.

Recommended fix High confidence

IBM Domino 8.5.3 FP6 IF7 (or Domino 9.0.1 FP3 IF3)

  1. 1. Identify the current IBM Domino version by checking the server console or using 'show version' command
  2. 2. Download IBM Domino 8.5.3 FP6 (Feature Pack 6) from IBM Fix Central or your authorized IBM rep
  3. 3. Apply IBM Domino 8.5.3 FP6 IF7 (Interim Fix 7) - this is the specific patch for CVE-2015-1902 per SPR KLYH9TSMLA
  4. 4. Alternatively, consider upgrading to IBM Domino 9.0.1 FP3 IF3 which also contains the fix
  5. 5. After applying the patch/interim fix, restart the Domino server
  6. 6. Verify the patch was applied by checking the fix list and confirming the server starts without errors
  7. 7. Test that BMP image processing works normally after the patch
Caveat Interim Fixes (IFs) are cumulative but test in non-production first as they may include other fixes that could affect custom configurations

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

Fix this in Domino Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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