dbcve.org
Hcl Devops DeployApplication · Hcltechsw

CVE-2025-0257

HIGH · 7.5 CVSS v3.1 Published 2025-04-02
Fix available
A fix is available. Upgrade to 7.1.2.23 / 7.2.3.16 or later.
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 DevOps Deploy / HCL Launch could allow unauthorized access to other services or potential exposure of sensitive data due to missing authentication in its Agent Relay service.

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 a missing authentication vulnerability in their Agent Relay service component. This allows unauthenticated attackers to potentially access other services or exfiltrate sensitive data by connecting to the Agent Relay without credentials.

MitigationImplement proper authentication mechanisms in the Agent Relay service or apply vendor-supplied patches to address the missing authentication. Restrict network exposure of the Agent Relay service until remediated.

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.6>= 8.1.0, < 8.1.1
Hcl LaunchApplication
Affected:>= 7.1.0.0, < 7.1.2.23>= 7.2.0.0, < 7.2.3.16>= 7.3.0.0, < 7.3.2.11

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 product and version
    Locate the HCL DevOps Deploy or HCL Launch installation directory and check the version file or use the product's version command. Typical locations include /opt/HCL or C:\HCL\ in the installation folder, or check the 'version.txt' or 'productVersion' file in the installation root.
    Affected if The installed version falls within the affected ranges: HCL DevOps Deploy < 8.0.1.6 or < 8.1.1; HCL Launch < 7.1.2.23, < 7.2.3.16, or < 7.3.2.11
  2. Confirm Agent Relay component is enabled
    Check the HCL Deploy or HCL Launch configuration for the Agent Relay service. Look for 'agentrelay' or 'relay' settings in the installation's conf or config directory, or check the component list via the product's administrative console.
    Affected if Agent Relay is installed and enabled as a component in the environment
  3. Verify Agent Relay network exposure
    Check the network listeners configuration for the Agent Relay service. Inspect the server.xml, bootstrap.yaml, or relay configuration files to identify the bind address and port (typically port 20080 or 8443 for relay). Use 'netstat' or 'ss' commands to confirm the service is listening on network interfaces.
    Affected if Agent Relay is listening on a non-localhost address or is accessible from the network without authentication restrictions
  4. Review Agent Relay authentication settings
    Examine the Agent Relay configuration files for authentication enforcement settings. Look for properties like 'requireAuthentication', 'authenticationEnabled', or similar security-related configuration in the relay configuration.
    Affected if Authentication is not required or is disabled for the Agent Relay service connections

The environment is affected if HCL DevOps Deploy or HCL Launch is installed with a version in the affected ranges AND the Agent Relay component is enabled and accessible without enforced authentication.

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.1.2.23 / 7.2.3.16 / 7.3.2.11 or later
Fixed in 7.1.2.237.2.3.167.3.2.11
Interim mitigation

Implement proper authentication mechanisms in the Agent Relay service or apply vendor-supplied patches to address the missing authentication. Restrict network exposure of the Agent Relay service until remediated.

Recommended fix High confidence

HCL DevOps Deploy: 8.0.1.6 or 8.1.1 | HCL Launch: 7.1.2.23, 7.2.3.16, or 7.3.2.11

  1. 1. Identify the currently deployed HCL DevOps Deploy or HCL Launch version and build number
  2. 2. For HCL DevOps Deploy: Upgrade to version 8.0.1.6 or 8.1.1 (depending on your current major version branch)
  3. 3. For HCL Launch: Upgrade to version 7.1.2.23, 7.2.3.16, or 7.3.2.11 (depending on your current major version branch)
  4. 4. Download the fixed version from HCL Software support portal (support.hcl-software.com)
  5. 5. Apply the upgrade following HCL's standard upgrade documentation
  6. 6. Verify the Agent Relay service is running with authentication enabled after upgrade
  7. 7. Test that Agent Relay connections work correctly with the fixed version
Caveat Review HCL release notes for any compatibility changes between your current version and the target fixed version before upgrading

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

Fix this in Hcl Devops Deploy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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