dbcve.org
Hcl LaunchApplication · Hcltechsw

CVE-2023-45701

MEDIUM · 6.5 CVSS v3.1 Published 2023-12-28
Fix available
A fix is available. Upgrade to after 7.3.2.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Launch could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system.

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 Launch returns detailed technical error messages directly to the browser, exposing sensitive system information such as stack traces, internal paths, or configuration details that could assist attackers in reconnaissance and further exploitation.

MitigationConfigure HCL Launch to display generic error messages to end users while logging detailed errors server-side; implement custom error pages and ensure production error handling suppresses verbose technical information.

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 LaunchApplication
Affected:>= 7.0.0.0, <= 7.0.5.18>= 7.1.0.0, <= 7.1.2.14>= 7.2.0.0, <= 7.2.3.7>= 7.3.0.0, <= 7.3.2.2

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

CVSS:3.1/AV:N/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. Identify installed HCL Launch version
    Access the HCL Launch web UI, navigate to the About or Settings section, or check the installation directory for version files. Typical locations include the server's installation folder or the 'server' subdirectory where version information is stored.
    Affected if The installed version falls within any of these ranges: 7.0.0.0-7.0.5.18, 7.1.0.0-7.1.2.14, 7.2.0.0-7.2.3.7, or 7.3.0.0-7.3.2.2
  2. Verify error response configuration
    Locate the HCL Launch server configuration files, typically found in the conf or config directory of the installation. Look for settings related to error pages, error handling, or debug mode.
    Affected if The configuration allows verbose technical error messages (stack traces, internal paths) to be displayed to end users, or debug mode is enabled in production
  3. Trigger a test error and inspect response
    Submit an invalid request to the HCL Launch server (such as accessing a non-existent resource or providing malformed input) and capture the HTTP response. Examine the response body for stack traces, Java class names, file paths, or configuration details.
    Affected if The browser returns detailed technical information such as Java stack traces, internal server paths, or configuration values instead of a generic error message

A user is affected if their HCL Launch version is within the listed ranges AND the server returns detailed stack traces or internal system information in error responses to the browser.

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 a release after 7.3.2.2
Interim mitigation

Configure HCL Launch to display generic error messages to end users while logging detailed errors server-side; implement custom error pages and ensure production error handling suppresses verbose technical information.

Recommended fix Moderate confidence

7.3.3.0 or later for 7.3.x line (or corresponding fixes for 7.0.x/7.1.x/7.2.x lines)

  1. 1. Identify your current HCL Launch version from the About page in the application.
  2. 2. Based on your current version line, plan upgrade to the next available release that includes the security fix.
  3. 3. For version 7.0.x: upgrade to 7.0.6.0 or later.
  4. 4. For version 7.1.x: upgrade to 7.1.3.0 or later.
  5. 5. For version 7.2.x: upgrade to 7.2.4.0 or later.
  6. 6. For version 7.3.x: upgrade to 7.3.3.0 or later.
  7. 7. Test the upgrade in a non-production environment before deploying to production.
  8. 8. After upgrade, verify that detailed technical error messages are no longer exposed in browser responses.
Caveat Review HCL release notes for your version line for any breaking changes or deprecation notices before upgrading

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

Fix this in Hcl Launch Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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