dbcve.org
DominoApplication · Hcltech

CVE-2022-38654

MEDIUM · 5.5 CVSS v3.1 Published 2022-11-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
HCL Domino is susceptible to an information disclosure vulnerability. In some scenarios, local calls made on the server to search the Domino directory will ignore xACL read restrictions. An authenticated attacker could leverage this vulnerability to access attributes from a user's person record.

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 confidence

HCL Domino contains an information disclosure vulnerability where local server-side calls to search the Domino directory bypass extended ACL (xACL) read restrictions. An authenticated attacker can exploit this to read sensitive attributes from user person records in the Domino directory.

MitigationApply the HCL Domino security patch for CVE-2022-38654 and review xACL configurations on the Domino directory to ensure proper restriction of sensitive user attributes.

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
DominoApplication
Affected:= 9.0.1= 10.0.0= 10.0.1= 11.0.1= 12.0

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed HCL Domino version
    Run 'show version' from the Domino server console, or check the program directory for version information files
    Affected if Installed version matches 9.0.1, 10.0.0, 10.0.1, 11.0.1, or 12.0
  2. Verify Domino Directory (names.nsf) ACL settings
    Open the Domino Directory database ACL in Domino Administrator and inspect the entries, particularly checking if xACL (extended ACL) is enabled for the directory
    Affected if xACL is enabled on the Domino Directory and contains entries with read restrictions on sensitive person record attributes
  3. Check for extended ACL (xACL) configuration on person documents
    Use Domino Designer to open names.nsf, locate a person document, and examine the Extended ACL tab to see which fields have restricted read access
    Affected if xACL restrictions exist but can be bypassed via local server-side directory searches
  4. Test directory search access with restricted account
    Use a low-privilege authenticated user account to perform a directory lookup or search operation locally on the server (e.g., via Domino URL commands or API)
    Affected if The authenticated user can read sensitive attributes (such as password hashes, certificate data, or other restricted fields) that should be blocked by xACL settings
  5. Review server configuration for local call permissions
    Examine the Domino server document in the Directory under Server > Server Configurations > Server_YourServerName, checking Security tab settings for 'Allow local server-side calls' or similar trust configurations
    Affected if Local server-side calls are permitted without proper restrictions

A user is affected if running a listed Domino version with xACL configured on the Domino Directory, and local server-side directory searches can bypass read restrictions on sensitive person record attributes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the HCL Domino security patch for CVE-2022-38654 and review xACL configurations on the Domino directory to ensure proper restriction of sensitive user attributes.

Recommended fix Moderate confidence

HCL Domino 11.0.2 or later (12.0.x recommended)

  1. 1. Identify current HCL Domino version using 'tell server version' command in Domino console
  2. 2. Review HCL Domino 11.0.2+ or 12.0.0+ release notes for CVE-2022-38654 fixed version information at support.hcltechsw.com
  3. 3. Plan upgrade to a version after the affected versions (11.0.1) that includes the security fix
  4. 4. Test upgrade in non-production environment before deploying to production
  5. 5. After upgrade, verify the xACL read restrictions are properly enforced on Domino directory searches
Caveat Review release notes for compatibility notes when upgrading between major versions (e.g., 11.x to 12.x)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Domino Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38654 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38654 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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