dbcve.org
Hcl Devops DeployApplication · Hcltechsw

CVE-2025-0256

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-24
Fix available
A fix is available. Upgrade to 7.0.5.26 / 7.1.2.22 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 DevOps Deploy / HCL Launch could allow an authenticated user to obtain sensitive information about other users on the system due to missing authorization for a function.

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 / HCL Launch contains a missing authorization vulnerability where an authenticated user can access sensitive information about other users on the system through a function that lacks proper authorization checks. This allows unauthorized enumeration or disclosure of user-related data.

MitigationApply the vendor-supplied patch or security update for CVE-2025-0256. Review user access controls and ensure all functions enforce proper authorization checks before exposing user data.

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.5= 8.1.0
Hcl LaunchApplication
Affected:>= 7.0.0.0, < 7.0.5.26>= 7.1.0.0, < 7.1.2.22>= 7.2.0.0, < 7.2.3.15>= 7.3.0.0, < 7.3.2.10

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 the installed HCL product
    Access the web UI and navigate to the About or System Information page, or check the installation directory for version files. HCL DevOps Deploy and HCL Launch are distinct products - confirm which one is installed.
    Affected if The system is running either HCL DevOps Deploy or HCL Launch
  2. Determine the installed version of HCL DevOps Deploy
    Check the version through the web UI Help > About, or inspect version files in the installation directory. Note the full version number (e.g., 8.0.1.4, 8.1.0).
    Affected if The version is 8.0.0.0 through 8.0.1.4, or exactly 8.1.0 (these versions are vulnerable)
  3. Determine the installed version of HCL Launch
    Check the version through the web UI Help > About, or inspect version files in the installation directory. Note the full version number (e.g., 7.3.2.9).
    Affected if The version falls in these vulnerable ranges: 7.0.0.0 through 7.0.5.25, 7.1.0.0 through 7.1.2.21, 7.2.0.0 through 7.2.3.14, or 7.3.0.0 through 7.3.2.9
  4. Verify if user-related API endpoints are accessible without proper authorization
    As an authenticated user, attempt to access user information endpoints or functions that should require elevated privileges. The vulnerability allows enumeration of other users' data through a function lacking authorization checks.
    Affected if A low-privileged authenticated user can view sensitive information about other users on the system

The environment is affected if HCL DevOps Deploy version is 8.0.0.0 through 8.0.1.4 or exactly 8.1.0, OR HCL Launch version is 7.0.0.0 through 7.0.5.25, 7.1.0.0 through 7.1.2.21, 7.2.0.0 through 7.2.3.14, or 7.3.0.0 through 7.3.2.9.

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.26 / 7.1.2.22 / 7.2.3.15 or later
Fixed in 7.0.5.267.1.2.227.2.3.15
Interim mitigation

Apply the vendor-supplied patch or security update for CVE-2025-0256. Review user access controls and ensure all functions enforce proper authorization checks before exposing user data.

Recommended fix High confidence

HCL DevOps Deploy 8.0.1.5+ or newer; HCL Launch 7.0.5.26+, 7.1.2.22+, 7.2.3.15+, or 7.3.2.10+

  1. Identify which HCL product (DevOps Deploy or Launch) and the specific version currently installed
  2. For HCL DevOps Deploy: Upgrade to version 8.0.1.5 or later, or to a release newer than 8.1.0
  3. For HCL Launch: Upgrade to version 7.0.5.26 or later if on 7.0.x; upgrade to 7.1.2.22 or later if on 7.1.x; upgrade to 7.2.3.15 or later if on 7.2.x; upgrade to 7.3.2.10 or later if on 7.3.x
  4. Download the appropriate fix from the HCL Support Portal at support.hcl-software.com
  5. Follow HCL's standard upgrade documentation to apply the update
  6. After upgrade, verify the fix by confirming authenticated users can no longer access other users' sensitive information without proper authorization
Caveat Review HCL release notes for any breaking 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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