CVE-2011-0919
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 · uneditedMultiple stack-based buffer overflows in the (1) POP3 and (2) IMAP services in IBM Lotus Domino allow remote attackers to execute arbitrary code via non-printable characters in an envelope sender address, aka SPR KLYH87LLVJ.
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 POP3 and IMAP services allows remote code execution via specially crafted non-printable characters in the envelope sender address. This is a pre-authentication vulnerability in the email service handling code.
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.
-
Verify IBM Lotus Domino is installedCheck for Domino processes (nserver.exe, n.pop3.exe, n.imap.exe) in Task Manager or running services, or look for Domino installation directory (typically C:\Lotus\Domino or /opt/ibm/lotus/domino)Affected if IBM Lotus Domino server software is present on the system
-
Confirm POP3 service is running and exposedCheck if the POP3 service (n.pop3.exe or similar Domino POP3 process) is running and listening on TCP port 110. Use 'netstat -an | findstr :110' or check service statusAffected if POP3 service is running and bound to a network-accessible IP address
-
Confirm IMAP service is running and exposedCheck if the IMAP service (n.imap.exe or similar Domino IMAP process) is running and listening on TCP port 143. Use 'netstat -an | findstr :143' or check service statusAffected if IMAP service is running and bound to a network-accessible IP address
-
Check Domino versionInspect Domino version through the server console, notes.ini file, or 'nserver -v' command. Since all versions are affected, any unpatched Domino installation with POP3/IMAP enabled is vulnerableAffected if Running an unpatched version of IBM Lotus Domino with POP3 or IMAP services enabled and network-accessible
A user is affected if IBM Lotus Domino is installed with POP3 or IMAP services enabled and exposed to the network on unpatched versions.
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 security patches or upgrade to a supported version. If patching is not immediately possible, restrict network access to POP3/IMAP services or disable these services until remediation is possible.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0919 — 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-0919 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