dbcve.org
Hcl LeapApplication · Hcltech

CVE-2023-37534

MEDIUM · 6.1 CVSS v3.1 Published 2025-04-24
Fix available
A fix is available. Upgrade to 9.3.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 URI protocol whitelist in HCL Leap allows script injection through query parameters.

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

HCL Leap contains an insufficient URI protocol whitelist that fails to properly validate the protocol scheme in URIs passed through query parameters, allowing attackers to inject malicious scripts (likely javascript: or other protocols) that could execute in the context of a user's session.

MitigationImplement strict allowlist validation for URI protocols in query parameters, rejecting any URI that does not use explicitly permitted protocols (typically http/https), and ensure all user-supplied URIs are properly sanitized before rendering.

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.4

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 HCL Leap installation version
    Locate the version information for your HCL Leap installation through the admin console, installation directory, or product metadata files. Common locations include the about page in the admin interface or version properties in the installation root.
    Affected if The installed version is any release prior to 9.3.4 (for example, 9.3.3, 9.3.2, 9.2.x, or earlier)
  2. Review query parameter handling
    Audit your HCL Leap application for endpoints or forms that accept URL or URI values through query parameters. Examine the application's parameter passing mechanisms to identify where user-supplied URIs could be processed.
    Affected if Your application accepts URI values via query parameters in any feature (for example, redirect parameters, form field URLs, or API endpoints)
  3. Inspect URI protocol validation logic
    Examine the application's input validation and sanitization code or configuration for how it handles URI schemes in query parameters. Look for any whitelist or blacklist mechanisms controlling permitted protocols.
    Affected if There is no strict protocol whitelist enforcement, or the validation can be bypassed, allowing non-http/https protocols to pass through
  4. Test for protocol injection
    If you have a test environment, submit a query parameter with a URI using a javascript: or other non-http protocol (for example, javascript:alert(1)) and observe whether the application accepts or renders it.
    Affected if The application accepts or reflects back URIs with non-whitelisted protocols like javascript: without rejection or sanitization

You are affected if your HCL Leap version is below 9.3.4 AND your application processes URI values in query parameters without strict protocol whitelist validation.

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.4 or later
Fixed in 9.3.4
Interim mitigation

Implement strict allowlist validation for URI protocols in query parameters, rejecting any URI that does not use explicitly permitted protocols (typically http/https), and ensure all user-supplied URIs are properly sanitized before rendering.

Recommended fix Moderate confidence

HCL Leap 9.3.4 or later

  1. 1. Back up your current HCL Leap installation and database
  2. 2. Review HCL Leap 9.3.4 release notes for any migration requirements
  3. 3. Download HCL Leap version 9.3.4 or later from HCL Software support portal (support.hcl-software.com)
  4. 4. Install the upgrade following HCL's standard upgrade documentation
  5. 5. After upgrade, verify the application is functioning correctly
  6. 6. Test that query parameter injection is no longer possible
Caveat Review release notes for any configuration or compatibility changes between your current version and 9.3.4; minor version upgrades within 9.x typically have minimal breaking changes

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

Fix this in Hcl Leap Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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