dbcve.org
Lotus DominoApplication · Ibm

CVE-2011-0914

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
Integer signedness error 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 client request, leading to a heap-based buffer overflow.

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

Integer signedness error in ndiiop.exe in the DIIOP (Domino Internet Inter-ORB Protocol) service of IBM Lotus Domino server before 8.5.3 allows remote attackers to execute arbitrary code via specially crafted GIOP client requests, resulting in a heap-based buffer overflow.

MitigationUpgrade to IBM Lotus Domino 8.5.3 or later to patch the vulnerability. If immediate patching is not feasible, block external network access to the DIIOP service port (default TCP 63148) using firewall rules to reduce exposure.

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. Check if DIIOP task is enabled on the Domino server
    Access the Domino console or Administrator, and run the command 'show task' to list all running server tasks. Alternatively, inspect the server configuration document in the Domino Directory under Server - All Server Tasks to see if DIIOP is listed as an enabled task.
    Affected if The DIIOP task appears in the running task list or is marked as enabled in the server configuration
  2. Determine the installed IBM Lotus Domino version
    Run the command 'show version' at the Domino server console, or locate the version information through the operating system's installed programs list. Compare the version number to the affected ranges: versions <= 8.5.2.2, or 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, or 5.0.6.
    Affected if The installed Domino version matches any version listed in the affected ranges
  3. Locate and verify the ndiiop.exe file version
    Find the file ndiiop.exe in the Domino program directory (typically in the Domino bin folder). Right-click the file and select Properties, then view the Version tab to obtain the file version. Alternatively, use the command 'nversion -d' or check the file properties via command line.
    Affected if The ndiiop.exe file exists and its version corresponds to a vulnerable Domino release
  4. Confirm the DIIOP network listener is active
    Run the command 'netstat -an | findstr 63148' on Windows or 'netstat -an | grep 63148' on Linux/Unix to check if TCP port 63148 (the default DIIOP port) is in a listening state. You can also use a network port scanner targeting this port from a remote system.
    Affected if TCP port 63148 or the configured DIIOP port is shown as LISTENING and accepting connections

The server is vulnerable if the DIIOP task is enabled and the installed Domino version matches any version in the affected ranges (8.5.2.2 and below, or the 4.6.x and 5.0.x series listed), with ndiiop.exe running and listening 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 to IBM Lotus Domino 8.5.3 or later to patch the vulnerability. If immediate patching is not feasible, block external network access to the DIIOP service port (default TCP 63148) using firewall rules to reduce exposure.

Recommended fix High confidence

Lotus Domino 8.5.3 or later

  1. Identify current Lotus Domino version by checking the Domino server console or using 'tell server version' command
  2. Plan upgrade to Lotus Domino 8.5.3 or later (8.5.3 fixes this vulnerability)
  3. Test the upgrade in a non-production environment first
  4. Schedule a maintenance window for the upgrade
  5. Perform a complete backup of Domino data, directories, and configuration files
  6. Stop the Domino server services
  7. Install Lotus Domino 8.5.3 or later on the server
  8. Start the Domino server and verify it starts successfully
Caveat Major version upgrades may introduce compatibility changes with existing applications, templates, or integrations; test thoroughly before production deployment

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
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,140
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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