dbcve.org
Hcl Devops DeployApplication · Hcltechsw

CVE-2024-42195

MEDIUM · 6.8 CVSS v3.1 Published 2024-12-05
Fix available
A fix is available. Upgrade to 7.0.5.25 / 7.1.2.21 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable

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 DevOps Deploy / HCL Launch is vulnerable to HTML injection. This vulnerability may allow a user to embed arbitrary HTML tags in the Web UI potentially leading to sensitive information disclosure.

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 DevOps Deploy and HCL Launch contain an HTML injection vulnerability in their Web UI. This allows authenticated users (or potentially attackers via stored payloads) to embed arbitrary HTML tags into web pages. Successful exploitation could enable session hijacking, credential theft, or phishing attacks by injecting malicious scripts or deceptive content.

MitigationImplement robust input validation and output encoding for all user-supplied content rendered in the Web UI. Apply context-aware sanitization to prevent HTML tag injection, and consider Content Security Policy (CSP) headers to mitigate script execution.

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 Devops DeployApplication
Affected:>= 8.0.0.0, < 8.0.1.4
Hcl LaunchApplication
Affected:>= 7.0.0.0, < 7.0.5.25>= 7.1.0.0, < 7.1.2.21>= 7.2.0.0, < 7.2.3.14>= 7.3.0.0, < 7.3.2.9

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 product
    Determine whether your environment has HCL DevOps Deploy or HCL Launch installed. Check your installation directory, documentation, or running services to confirm which product is present.
    Affected if The product is either HCL DevOps Deploy or HCL Launch
  2. Determine installed version
    Locate the version information for your installation. This is typically accessible through the Web UI login page, about section, or by checking version files in the installation directory.
    Affected if The version falls within any of these ranges: DevOps Deploy >= 8.0.0.0 and < 8.0.1.4; Launch >= 7.0.0.0 and < 7.0.5.25, >= 7.1.0.0 and < 7.1.2.21, >= 7.2.0.0 and < 7.2.3.14, or >= 7.3.0.0 and < 7.3.2.9
  3. Verify Web UI accessibility
    Confirm that the HCL Web UI is accessible to users. This vulnerability exists in the Web UI component, so an accessible interface is required for exploitation.
    Affected if The Web UI is exposed and accessible to authenticated users or potential attackers
  4. Review user-supplied content in Web UI
    Inspect any areas of the Web UI where users can input or display custom content (such as descriptions, notes, custom properties, or names). Look for unescaped HTML tags or script elements.
    Affected if User-supplied content is rendered without proper HTML encoding or sanitization in the Web UI

You are affected if you have HCL DevOps Deploy (8.0.0.0 to < 8.0.1.4) or HCL Launch (7.0.0.0 to < 7.0.5.25, 7.1.0.0 to < 7.1.2.21, 7.2.0.0 to < 7.2.3.14, or 7.3.0.0 to < 7.3.2.9) with an accessible Web UI where user input is rendered without sanitization.

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 7.0.5.25 / 7.1.2.21 / 7.2.3.14 or later
Fixed in 7.0.5.257.1.2.217.2.3.14
Interim mitigation

Implement robust input validation and output encoding for all user-supplied content rendered in the Web UI. Apply context-aware sanitization to prevent HTML tag injection, and consider Content Security Policy (CSP) headers to mitigate script execution.

Recommended fix Moderate confidence

HCL DevOps Deploy 8.0.1.4 or later; HCL Launch 7.0.5.25, 7.1.2.21, 7.2.3.14, or 7.3.2.9 or later (depending on your current major.minor version)

  1. 1. Back up your current HCL Deploy or HCL Launch installation and database before upgrading.
  2. 2. Download the fixed version from the HCL Software Support Portal at support.hcl-software.com.
  3. 3. Stop the HCL Deploy or HCL Launch services.
  4. 4. Install or upgrade to the appropriate fixed version for your product line.
  5. 5. Verify the upgrade was successful and restart the services.
  6. 6. Test that the HTML injection vulnerability is remediated by attempting to inject HTML in affected input fields.
Caveat Review HCL release notes for your specific version upgrade path for any configuration or compatibility considerations

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

Fix this in Hcl Devops Deploy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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