dbcve.org
DominoApplication · Ibm

CVE-2015-1903

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 KLYH9TSN3Y.

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

IBM Domino contains a stack-based buffer overflow vulnerability in its BMP image processing functionality. Remote attackers can exploit this by sending a specially crafted BMP image to the Domino server, potentially allowing arbitrary code execution with the privileges of the Domino service.

MitigationApply IBM Domino version 8.5.3 FP6 IF7 or 9.0.1 FP3 IF3 or later. Until patches can be deployed, consider blocking or sanitizing BMP image uploads/attachments and isolating affected systems from 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 the installed Domino version
    Run the command 'tell server version' from the Domino server console, or check the version information in the Domino program directory
    Affected if The version matches 8.5.0, 8.5.1, 8.5.2, 8.5.3, or 9.0.1 exactly
  2. Determine if BMP image processing is accessible
    Check whether the Domino server is configured to process or render BMP images through HTTP attachments, email attachments, or database view thumbnail rendering
    Affected if The server accepts or processes BMP image files in any capacity
  3. Review attachment handling configuration
    Examine Domino configuration documents and notes.ini settings related to attachment handling, particularly for SMTP, HTTP, and database attachment capabilities
    Affected if BMP file attachments are permitted through email, HTTP uploads, or database resources
  4. Assess network accessibility of Domino services
    Review firewall rules and network accessibility of Domino HTTP, SMTP, and IMAP services that could receive BMP attachments
    Affected if The Domino server accepts connections from untrusted networks on ports used for attachment submission

The environment is affected if the installed Domino version is exactly 8.5.0, 8.5.1, 8.5.2, 8.5.3, or 9.0.1 and the server processes BMP images via any accessible service.

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 IBM Domino version 8.5.3 FP6 IF7 or 9.0.1 FP3 IF3 or later. Until patches can be deployed, consider blocking or sanitizing BMP image uploads/attachments and isolating affected systems from untrusted networks.

Recommended fix High confidence

IBM Domino 8.5.3 FP6 IF7 (or Domino 9.0.1 FP3 IF3 for longer support lifecycle)

  1. 1. Identify current IBM Domino version by checking the Domino server console or using 'tell server version' command
  2. 2. Download IBM Domino 8.5.3 FP6 IF7 or later from IBM Fix Central (https://www-945.ibm.com/support/fixcentral/)
  3. 3. Review IBM Domino upgrade documentation and release notes before proceeding
  4. 4. Back up the Domino server data directory, directory, and all NSF databases
  5. 5. Stop the IBM Domino server using 'quit' command from the server console
  6. 6. Install IBM Domino 8.5.3 FP6 IF7 (or migrate to Domino 9.0.1 with FP3 IF3 for longer-term support)
  7. 7. Restart the IBM Domino server and verify successful startup
  8. 8. Verify the fix by confirming the installed version and IF level matches the patched release
Caveat Review IBM Domino release notes for any configuration or compatibility changes between versions; test thoroughly in non-production environment before production deployment

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

Fix this in Domino Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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