What is the CVSS score of CVE-2025-0273?

CVE-2025-0273 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Hcl Devops Deploy are affected by CVE-2025-0273?

CVE-2025-0273 presents moderate security risk, a log file exposure vulnerability rated CVSS 5.5. This could allow unauthorized file access.

How to fix or mitigate CVE-2025-0273?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Review data exposure and access controls.

Hcl Devops Deploy CVE-2025-0273

MEDIUM

Insertion of Sensitive Information into Log File (CWE-532)

2025-03-27 psirt@hcl.com

Information Disclosure Hcl Devops Deploy Hcl Launch

5.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:33 vuln.today

CVE Published

Mar 27, 2025 - 05:15 nvd

MEDIUM 5.5

DescriptionCVE.org

HCL DevOps Deploy / HCL Launch stores potentially sensitive authentication token information in log files that could be read by a local user.

AnalysisAI

HCL DevOps Deploy / HCL Launch stores potentially sensitive authentication token information in log files that could be read by a local user. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-532. HCL DevOps Deploy / HCL Launch stores potentially sensitive authentication token information in log files that could be read by a local user. Affected products include: Hcltechsw Hcl Devops Deploy, Hcltechsw Hcl Launch.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.