CVE-2024-23588
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 · uneditedHCL Nomad server on Domino fails to properly handle users configured with limited Domino access resulting in a possible denial of service vulnerability.
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 · moderate confidenceHCL Nomad server on Domino contains a denial of service vulnerability where the server fails to properly handle users configured with limited Domino access, causing the service to become unavailable when these users attempt to connect or perform operations.
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< 1.0.12CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 HCL Nomad Server on Domino is installedLook for the Nomad server installation directory, typically under the Domino program folder, or check for the nomad.exe process running on the serverAffected if The product is not installed or not running - not affected
-
Identify the installed Nomad Server versionCheck the version of the Nomad server binary (nomad.exe) or view the version in the installation manifest/readme file. Compare against the affected version range of < 1.0.12Affected if Version is 1.0.11 or lower, or any version below 1.0.12
-
Verify the Domino Directory contains users with limited accessOpen the Domino Directory (names.nsf) and review user documents in the People view. Look for users where the field 'Allow Notes/Domino login' is disabled, or where access is restricted via explicit ACL settings rather than full accessAffected if There are users configured with limited Domino access (restricted login enabled) in the Domino Directory
-
Check if Nomad server is currently accessibleAttempt to connect to the Nomad server URL (typically port 8080 or 8443) or check if the nomad.exe process is responding to requestsAffected if The server is unresponsive or has recently crashed, especially after user connections from limited-access accounts
-
Review server console logs for access errorsExamine Domino console log or nomad.log for entries showing server failures, connection timeouts, or crash events coinciding with limited-access user activityAffected if Logs show repeated failures or crashes tied to connections from users with limited Domino access
The environment is affected if HCL Nomad Server on Domino is installed with version 1.0.11 or lower AND there are users configured with limited Domino access in the Domino Directory, causing service unavailability when these users connect.
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.
dbcve · scoped1.0.12
Review and verify user access configurations in Domino Directory; apply vendor patches when available; consider implementing rate limiting or monitoring for unusual access patterns.
1.0.12
- Obtain HCL Nomad Server on Domino version 1.0.12 from HCL's official download channels or support.hcltechsw.com
- Follow HCL's standard upgrade procedure for Nomad Server on Domino to install version 1.0.12
- Verify the upgrade was successful by checking the Nomad Server version
- Restart the Domino server if required by the upgrade process
- Test that Nomad Server functions correctly with users configured with limited Domino access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23588 — 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-2024-23588 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