dbcve.org
Hcl Devops DeployApplication · Hcltechsw

CVE-2025-0273

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-27
Fix available
A fix is available. Upgrade to 7.1.2.22 / 7.2.3.15 or later.
See remediation →
57/100
Remediation priority · Elevated
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 stores potentially sensitive authentication token information in log files that could be read by a local user.

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 store sensitive authentication token information in log files, which could be read by a local user with access to those files. This represents an information disclosure vulnerability enabling potential credential theft.

MitigationRestrict log file permissions to prevent unauthorized local access, implement log sanitization to exclude authentication tokens, and rotate any potentially exposed credentials.

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, < 8.1.0.1
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.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/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 product and version
    Locate the HCL DevOps Deploy or HCL Launch installation and check the version information (typically found in product metadata files, about dialog, or version.properties)
    Affected if The installed version falls within: Deploy 8.0.0.0 to <8.0.1.5 or 8.1.0 to <8.1.0.1; Launch 7.0.0.0 to 7.0.5.26, 7.1.0.0 to <7.1.2.22, 7.2.0.0 to <7.2.3.15, or 7.3.0.0 to 7.3.2.9
  2. Locate log directories
    Find the log directories used by the installation (commonly in the installation root under var/log or logs subdirectory)
    Affected if Log directories exist and contain application logs
  3. Inspect log files for authentication tokens
    Search log files for patterns resembling authentication tokens, API keys, session identifiers, or credential strings (use grep or similar tools to search for keywords like 'token', 'auth', 'password', 'credential', 'bearer', 'api key')
    Affected if Log files contain any readable authentication token or credential-like strings
  4. Verify log file permissions
    Check file system permissions on log files to determine if unauthorized local users can read them (use ls -la on log files)
    Affected if Log files are readable by users other than the application owner or restricted administrator accounts

You are affected if your installed version falls within the affected ranges AND log files contain exposed authentication tokens readable by unauthorized local users.

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.22 / 7.2.3.15 / 8.0.1.5 or later
Fixed in 7.1.2.227.2.3.158.0.1.5
Interim mitigation

Restrict log file permissions to prevent unauthorized local access, implement log sanitization to exclude authentication tokens, and rotate any potentially exposed credentials.

Recommended fix Moderate confidence

HCL DevOps Deploy: 8.0.1.5 or 8.1.0.1 | HCL Launch: 7.1.2.22, 7.2.3.15, or 7.3.2.10 (or later supported versions)

  1. 1. Identify the currently installed HCL DevOps Deploy or HCL Launch version using the product's version information
  2. 2. For HCL DevOps Deploy users on 8.0.0.0 through 8.0.1.4: Upgrade to version 8.0.1.5 or later
  3. 3. For HCL DevOps Deploy users on 8.1.0: Upgrade to version 8.1.0.1 or later
  4. 4. For HCL Launch users on 7.0.0.0 through 7.0.5.26: Upgrade to version 7.1.2.22 or later (or a later supported major version)
  5. 5. For HCL Launch users on 7.1.0.0 through 7.1.2.21: Upgrade to version 7.1.2.22 or later
  6. 6. For HCL Launch users on 7.2.0.0 through 7.2.3.14: Upgrade to version 7.2.3.15 or later
  7. 7. For HCL Launch users on 7.3.0.0 through 7.3.2.9: Upgrade to version 7.3.2.10 or later
  8. 8. After upgrade, review log files to confirm no sensitive authentication tokens are being written
Caveat Review HCL release notes for your specific version upgrade path for any compatibility notes or deprecated features

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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