dbcve.org
Lotus DominoApplication · Ibm

CVE-2011-0915

HIGH · 10.0 CVSS v2.0 Published 2011-02-08
Fix available
A fix is available. Upgrade to after 8.5.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 nrouter.exe in IBM Lotus Domino before 8.5.3 allows remote attackers to execute arbitrary code via a long name parameter in a Content-Type header in a malformed Notes calendar (aka iCalendar or iCal) meeting request, aka SPR KLYH87LL23.

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

Stack-based buffer overflow in IBM Lotus Domino's nrouter.exe component allows remote attackers to execute arbitrary code via a malformed iCalendar (iCal) meeting request containing an excessively long name parameter in the Content-Type header.

MitigationUpgrade IBM Lotus Domino to version 8.5.3 or later to patch the vulnerability; alternatively, consider network-level filtering of malformed iCal requests and restricting external calendar processing until the upgrade can be performed.

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
Lotus DominoApplication
Affected:<= 8.5.2.2= 4.6.1= 4.6.3= 4.6.4= 5.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.4a= 5.0.5= 5.0.6

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. Verify IBM Lotus Domino installation
    Locate the Domino installation directory, typically under C:\Lotus\Domino or /notesdata on Windows or Linux/Unix servers. Check for the presence of the Domino program files.
    Affected if IBM Lotus Domino server software is not installed on the system.
  2. Determine Domino server version
    Check the version by viewing the Domino Program Directory for a version file, or run 'tell http version' from the Domino server console, or examine the properties of nrouter.exe.
    Affected if The installed version matches or falls within: 4.6.1, 4.6.3, 4.6.4, 5.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.4a, 5.0.5, 5.0.6, or any version 8.5.2.2 or earlier.
  3. Confirm nrouter.exe component exists
    Locate nrouter.exe within the Domino program directory. This is the Notes Router executable that handles mail and calendar routing including iCalendar processing.
    Affected if The nrouter.exe file exists in the Domino installation directory.
  4. Check if calendar services are enabled
    From the Domino server console, run 'show config' and look for Calendar configuration settings, or check the Domino Directory (names.nsf) for Calendar Server document settings. Also verify the router task is enabled by running 'show tasks'.
    Affected if The Domino server has the Router task running and calendar processing is enabled, allowing incoming iCalendar meeting requests to be processed.
  5. Identify external calendar exposure
    Review server configuration documents for 'Allow remote calendar requests' or 'Process incoming iCal' settings. Check if the server accepts iCalendar data from external or untrusted sources via HTTP or SMTP.
    Affected if The Domino server is configured to accept or process iCalendar meeting requests from external sources, particularly via SMTP with malformed Content-Type headers.

The environment is affected if IBM Lotus Domino is installed with a version matching the affected list and the nrouter.exe component is active with calendar/iCalendar processing enabled for incoming requests.

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
Upgrade available Upgrade to a release after 8.5.2.2
Interim mitigation

Upgrade IBM Lotus Domino to version 8.5.3 or later to patch the vulnerability; alternatively, consider network-level filtering of malformed iCal requests and restricting external calendar processing until the upgrade can be performed.

Recommended fix High confidence

IBM Lotus Domino 8.5.3 or later

  1. Download IBM Lotus Domino 8.5.3 or later from IBM Fix Central or your authorized IBM distributor
  2. Review IBM Lotus Domino upgrade documentation for your current version
  3. Plan maintenance window for the upgrade process
  4. Backup your existing Domino data and configuration
  5. Install Domino 8.5.3 or later on your servers
  6. Verify the nrouter.exe component is updated to the fixed version
  7. Test calendar/iCalendar functionality after upgrade
  8. Deploy to production environment
Caveat Major version upgrades may introduce compatibility changes with existing applications or integrations; test thoroughly in a non-production environment before deploying

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

Fix this in Lotus 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 upgrade done

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-2011-0915 — 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-2011-0915 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