dbcve.org
DominoApplication · Hcltech

CVE-2022-27558

HIGH · 7.5 CVSS v3.1 Published 2022-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 iNotes is susceptible to a Broken Password Strength Checks vulnerability. Custom password policies are not enforced on certain iNotes forms which could allow users to set weak passwords, leading to easier cracking.

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 iNotes fails to enforce custom password policies on certain web forms, allowing users to set weak passwords that bypass organizational security requirements. This broken password strength check vulnerability affects specific iNotes interfaces where password validation logic is missing or bypassed, enabling easier credential cracking through brute force or dictionary attacks.

MitigationReview and update all iNotes password-related forms to ensure custom password policies are consistently enforced, including implementing proper validation on any forms currently exempt from policy checks.

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:= 12.0.1
Hcl InotesApplication
Affected:= 12.0.1

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

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

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

  1. Identify installed HCL Domino and iNotes version
    Check the Domino server and iNotes version using the Domino Administration client or by querying the server's Program directory for version information. On the server console, you can also use 'show version' command.
    Affected if The installed version is exactly 12.0.1 for either Domino or iNotes components.
  2. Determine if custom password policies are configured
    Review the Domino Directory (names.nsf) for any custom password policy documents created in the Policies view. Look for Password Security settings that define minimum length, complexity requirements, or dictionary restrictions.
    Affected if Custom password policies exist and are assigned to users or groups in the organization.
  3. Identify password-related web forms in use
    Examine the iNotes database templates (mail*.ntf) on the server to locate password change and password reset web forms. Check which templates are in use by viewing the mail file configuration.
    Affected if iNotes web forms for password changes are present and accessible to end users.
  4. Verify password validation is enforced on all forms
    Test password change functionality by attempting to set a weak password (e.g., short or simple password) through the iNotes web interface. Compare against the configured custom password policy requirements.
    Affected if A weak password that violates the custom policy is accepted without error or rejection.

You are affected if running exactly version 12.0.1 of HCL Domino or iNotes AND have custom password policies configured but can still set weak passwords through certain iNotes web forms.

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

Review and update all iNotes password-related forms to ensure custom password policies are consistently enforced, including implementing proper validation on any forms currently exempt from policy checks.

Recommended fix Moderate confidence

HCL Domino/iNotes 12.0.1 FP1 or later security fix (check HCL support for specific fixed release)

  1. 1. Identify the current HCL Domino and iNotes version in your environment (confirm it is 12.0.1)
  2. 2. Check HCL support portal (support.hcltechsw.com) for the latest available fix pack or security fix for this vulnerability
  3. 3. Download and apply the appropriate fix pack or security patch that addresses CVE-2022-27558
  4. 4. Verify the patch was applied successfully by checking the iNotes version or Domino console
  5. 5. Test password policy enforcement on iNotes forms to confirm the vulnerability is remediated
Caveat Standard HCL fix pack apply process - test in non-production first, review release notes for any compatibility notes

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

Fix this in Domino Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27558 — 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-27558 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