dbcve.org
Lotus DominoApplication · Ibm

CVE-2011-0913

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 ndiiop.exe in the DIIOP implementation in the server in IBM Lotus Domino before 8.5.3 allows remote attackers to execute arbitrary code via a GIOP getEnvironmentString request, related to the local variable cache.

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 ndiiop.exe in the DIIOP implementation of IBM Lotus Domino servers prior to version 8.5.3. The vulnerability allows remote attackers to execute arbitrary code via a specially crafted GIOP getEnvironmentString request that overflows a local variable cache buffer on the stack.

MitigationUpgrade IBM Lotus Domino server to version 8.5.3 or later to patch the vulnerability. If the DIIOP service is not required, it should be disabled to reduce the attack surface.

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. Identify installed IBM Lotus Domino version
    Run 'tell http version' from the Domino server console, or check the Domino version via the Windows registry at HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Domino or Linux equivalent in /opt/lotus/notes/latest/lin or look at the 'Version' field in the Domino Server document in the Domino Directory.
    Affected if The installed version matches any of the affected versions: 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 from 6.x through 8.5.2.2.
  2. Verify DIIOP task is enabled and running
    From the Domino server console, run 'show tasks' and look for 'DIIOP' in the output, or check the Server Tasks document in the Domino Directory to confirm DIIOP is listed as an enabled internet task.
    Affected if The DIIOP task is loaded and running on the server.
  3. Confirm ndiiop.exe process is active
    On Windows, open Task Manager or run 'tasklist | findstr ndiiop' from command prompt. On Linux, run 'ps -ef | grep ndiiop' to check if the ndiiop process is running.
    Affected if The ndiiop.exe process is running on the system.
  4. Check DIIOP port accessibility
    Run 'telnet <server> 63148' or use a network scanner to verify port 63148 (default DIIOP port) is open and accepting connections, or check the DIIOP task configuration in the Domino Directory for the configured port.
    Affected if Port 63148 or the configured DIIOP port is accessible from a network, indicating the vulnerable service is exposed.

The server is affected if it runs a Lotus Domino version prior to 8.5.3 AND has the DIIOP task enabled with ndiiop.exe actively running and accessible on 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
Upgrade available Upgrade to a release after 8.5.2.2
Interim mitigation

Upgrade IBM Lotus Domino server to version 8.5.3 or later to patch the vulnerability. If the DIIOP service is not required, it should be disabled to reduce the attack surface.

Recommended fix High confidence

IBM Lotus Domino 8.5.3 or later

  1. 1. Review IBM Lotus Domino 8.5.3 release notes and upgrade documentation for compatibility requirements
  2. 2. Create a complete backup of the Domino server data directory, directory catalog, and configuration files
  3. 3. Test the upgrade in a non-production environment first to verify application compatibility
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Stop all Domino server services before upgrading
  6. 6. Install IBM Lotus Domino 8.5.3 or later from IBM's official download channels
  7. 7. Verify the DIIOP task (ndiiop.exe) version matches the updated release
  8. 8. Restart Domino server services
Caveat Ensure custom DIIOP/CORBA applications are compatible with 8.5.3 as minor version upgrades may introduce API behavior changes

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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