dbcve.org
Hcl LeapApplication · Hcltech

CVE-2023-45720

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-24
Fix available
A fix is available. Upgrade to 9.3.5 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Insufficient default configuration in HCL Leap allows anonymous access to directory information.

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 confidence

CVE-2023-45720 is an insufficient default configuration vulnerability in HCL Leap that allows unauthenticated attackers to access directory information. The application's default configuration does not properly restrict access to directory/user listing functionality, enabling anonymous enumeration of potentially sensitive organizational information.

MitigationModify the default configuration in HCL Leap to disable anonymous access to directory information and enforce proper authentication controls for directory-related endpoints.

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
Hcl LeapApplication
Affected:< 9.3.5

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Leap version
    Check the HCL Leap version by accessing the About page in the application or reviewing the installation manifest. On the server, this is typically found in the product installation directory or via the /domino/ leap About URL.
    Affected if The installed version is any release prior to 9.3.5 (e.g., 9.3.4, 9.3.3, 9.2.x, etc.)
  2. Verify directory access configuration
    Locate the HCL Leap configuration file (typically leapConfig.xml or similar configuration files in the conf directory). Search for settings related to directory access, user listing, or anonymous authentication.
    Affected if The configuration contains settings that allow anonymous or unauthenticated access to directory-related endpoints or user information.
  3. Test directory endpoint accessibility
    Attempt to access common directory or user listing endpoints without authentication. These may include URLs like /leap/ directory APIs, user lookup endpoints, or organizational listing functions.
    Affected if Directory information, user listings, or organizational data is returned without requiring login credentials.
  4. Review authentication settings for directory features
    Examine the authentication configuration panel in HCL Leap admin console. Look for settings controlling anonymous access to directory, user lookup, or organizational browser features.
    Affected if Anonymous access is enabled for directory or user enumeration features.

A user is affected if running HCL Leap version below 9.3.5 AND the default configuration allows unauthenticated access to directory information or user listing functionality.

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
Upgrade available Upgrade to 9.3.5 or later
Fixed in 9.3.5
Interim mitigation

Modify the default configuration in HCL Leap to disable anonymous access to directory information and enforce proper authentication controls for directory-related endpoints.

Recommended fix Moderate confidence

HCL Leap 9.3.5

  1. Ensure you have a complete backup of your HCL Leap environment including database and configuration files
  2. Review HCL Leap 9.3.5 release notes for any prerequisite changes
  3. Download HCL Leap version 9.3.5 or later from the HCL support portal
  4. Stop the HCL Leap server services before applying the upgrade
  5. Apply the upgrade following the standard HCL Leap upgrade documentation
  6. After upgrade, verify the directory access configuration settings in the administration console
  7. Restart HCL Leap services
  8. Confirm anonymous access to directory information is no longer allowed
Caveat Review release notes for any configuration or migration requirements specific to 9.3.5

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

Fix this in Hcl Leap Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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