CVE-2011-0918
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 · uneditedStack-based buffer overflow in the NRouter (aka Router) service in IBM Lotus Domino allows remote attackers to execute arbitrary code via long filenames associated with Content-ID and ATTACH:CID headers in attachments in malformed calendar-request e-mail messages, aka SPR KLYH87LKRE.
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 confidenceStack-based buffer overflow in IBM Lotus Domino's NRouter service allows remote attackers to execute arbitrary code via long filenames in Content-ID and ATTACH:CID headers within malformed calendar-request e-mail message attachments.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm IBM Lotus Domino installationLocate Domino installation directory (typically C:\Lotus\Domino or /opt/ibm/lotus/domino) and verify the presence of Domino executables (nrouter.exe, lotus.exe, etc.)Affected if IBM Lotus Domino server software is present on the system
-
Identify Domino versionRun 'domino -version' or check the version displayed in Domino Administrator, or read the version from the notes.ini file or Domino program directoryAffected if Any version of IBM Lotus Domino is installed (all versions are affected)
-
Verify NRouter service is runningCheck Windows Services (if Windows) for 'Lotus Domino Router' service status, or on Linux/Unix check running processes for nrouter processAffected if NRouter service is active and accepting mail connections
-
Confirm calendar request processing is enabledExamine Domino server configuration document in Domino Directory (names.nsf) under Server > Configurations > Configuration Settings > Router > SMTP - check if 'Calendar processing' is enabled, or check notes.ini for CalendarServer=1Affected if Calendar request processing is enabled on the Domino server
-
Check SMTP/inbound mail configurationReview Router/SMTP settings in Domino Directory to confirm the server accepts external SMTP mail connectionsAffected if Server accepts inbound SMTP mail (direct or via gateway)
-
Inspect NRouter configuration for CID attachment handlingReview router configuration files and notes.ini for ATTACH:CID and Content-ID header processing settingsAffected if CID header processing for attachments is not explicitly disabled
The environment is affected if IBM Lotus Domino with NRouter service is installed, any version, with calendar request processing enabled and accepting inbound mail.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply IBM Lotus Domino patches or upgrade to a fixed version; consider disabling or filtering calendar request processing at the network perimeter until patched.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0918 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-0918 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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