CVE-2011-1393
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 · uneditedUnspecified vulnerability in the authentication functionality in the server in IBM Lotus Domino 8.x before 8.5.2 FP4 allows remote attackers to cause a denial of service (daemon crash) via a crafted Notes RPC packet.
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 confidenceA denial of service vulnerability in IBM Lotus Domino server versions 8.x before 8.5.2 FP4 allows remote attackers to crash the Domino daemon by sending a crafted Notes RPC packet to the authentication component. The vulnerability is in the unspecified authentication functionality and requires no authentication to exploit.
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<= 8.5.2= 8.0= 8.0.1= 8.0.2= 8.0.2.1= 8.0.2.2= 8.0.2.3= 8.0.2.4= 8.0.2.5= 8.0.2.6= 8.0.5= 8.5.0CVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Determine installed Domino versionConnect to Domino server console (via telnet to console port or remote console) and run command: 'show version' or 'tell http platform version'. Alternatively, check the Domino Administrator client server status which displays the version.Affected if Version is 8.0.x, 8.5.0, 8.5.1, or 8.5.2 without FP4 applied
-
Confirm exact release and FP levelIf version shows 8.5.2, check whether Fix Pack 4 (FP4) is installed. Run 'show fixes' on Domino console or check IBM fix list documentation for installed iFixes.Affected if 8.5.2 is shown without FP4 or subsequent fixes applied
-
Verify Domino daemon status after restartCheck if Domino server has been experiencing unexpected crashes or daemon failures. Review Domino console logs (log.nsf) or system event logs for crash events around the time of external network access.Affected if Server has crashed repeatedly and version falls within affected range
User is affected if running IBM Lotus Domino version 8.0.x, 8.5.0, 8.5.1, or 8.5.2 without FP4 applied, and the server is network-accessible since exploitation requires no authentication.
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 dataUpgrade IBM Lotus Domino to version 8.5.2 FP4 or later, which contains the fix for this vulnerability. Apply the fix pack through standard IBM IBM iFix/Lotus maintenance channels.
- Consultation6.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1393 — 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-1393 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