CVE-2023-37495
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 · uneditedInternet passwords stored in Person documents in the Domino® Directory created using the "Add Person" action on the People & Groups tab in the Domino® Administrator are secured using a cryptographically weak hash algorithm. This could enable attackers with access to the hashed value to determine a user's password, e.g. using a brute force attack. This issue does not impact Person documents created through user registration https://help.hcltechsw.com/domino/10.0.1/admin/conf_userregistration_c.html .
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 confidenceInternet passwords in HCL Domino Person documents created via the 'Add Person' action in Domino Administrator are hashed using a cryptographically weak algorithm. Attackers with access to the stored hashes could potentially recover passwords through brute force attacks. This does not affect Person documents created through the user registration process.
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>= 9.0, < 14.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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Domino version is within affected rangeCheck the installed HCL Domino version. On the Domino server console or in Domino Administrator, look at the server document or use 'show version' command. Confirm the version is >= 9.0 and < 14.0.Affected if Installed version falls within 9.0 <= version < 14.0
-
Identify Person documents in the directoryAccess the Domino Directory (names.nsf) and locate Person documents. In Domino Administrator, browse the Directory > People view, or query the Domino Directory database for all documents with form type 'Person'.Affected if Person documents exist in the Domino Directory database
-
Determine creation method of Person documentsExamine how each Person document was created. Check the document properties or flags that distinguish 'Add Person' action creation from the standard user registration process. Look for a marker, flag, or field that indicates whether the document was created via Domino Administrator's 'Add Person' action versus the user registration feature.Affected if Person documents were created using Domino Administrator's 'Add Person' action rather than the user registration process
-
Inspect password hash algorithm usedFor Person documents identified as created via 'Add Person' action, examine the password hash stored in the internetPassword field or similar password field. Check the cryptographic algorithm used - look for weak hashing indicators such as older hash formats, shorter hash outputs, or lack of salt.Affected if Password hashes use a cryptographically weak algorithm (weaker than current Domino registration defaults)
-
Assess exposure riskDetermine if attackers could access the stored password hashes. Check file system permissions on names.nsf and the data directory, review who has administrative access, and evaluate whether the Domino Directory database is replicated or accessible externally.Affected if The password hash storage is accessible to unauthorized users who could perform offline brute force attacks
User is affected if running Domino 9.0-14.0 and has Person documents created via Domino Administrator's 'Add Person' action with weak password hashing that could be accessed by attackers for brute force recovery.
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 · scoped14.0
Use the user registration feature instead of the 'Add Person' action for creating Person documents.等待官方补丁修复弱哈希算法问题。
HCL Domino 14.0 or later
- Upgrade HCL Domino server to version 14.0 or later to resolve the weak password hashing vulnerability
- After upgrade, verify that new Person documents created via 'Add Person' use strong password hashing
- For existing affected Person documents, consider re-creating them through user registration (which uses strong hashing) or implementing additional access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37495 — 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-2023-37495 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