CVE-2025-0250VulnerabilityPublished 24 Jul 2025

CVE-2025-0250: HCL Software IEM · Cleartext Transmission

Affects HCL Software IEMSource CVE Database V5

Not known to be exploited · CVSS 2.2 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

2.2Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
HCL Software IEM	Affected =1.2	Fixed in–

AI-suggested

European organizations should implement the following specific mitigations: 1) Ensure that all communications involving HCL IEM, especially those transmitting authentication tokens, are secured using strong encryption protocols such as TLS 1.2 or higher. 2) Review and enforce secure cookie attributes, including 'Secure' and 'HttpOnly' flags, to prevent token exposure via client-side scripts and ensure transmission only over encrypted channels. 3) Apply network segmentation and monitoring to detect anomalous traffic that could indicate token interception attempts. 4) Limit the lifetime and scope of authorization tokens to reduce the window of opportunity for misuse if intercepted. 5) Regularly audit and update HCL IEM installations and monitor vendor communications for patches addressing this vulnerability. 6) Educate privileged users about the risks of token exposure and enforce strict access controls to minimize the number of users with high privileges. 7) Employ intrusion detection systems capable of identifying suspicious network activities related to token theft or replay attacks.

Description

HCL IEM is affected by an authorization token sent in cookie vulnerability. A token used for authentication and authorization is being handled in a manner that may increase its exposure to security risks.

Impact

For European organizations using HCL IEM version 1.2, this vulnerability poses a confidentiality risk. If an attacker can intercept the authorization token, they may impersonate legitimate users or escalate privileges, potentially leading to unauthorized access to monitoring and management functions within the IEM platform. Although the vulnerability requires high privileges to exploit and has a low impact score, organizations operating in sectors with stringent data protection regulations such as GDPR must consider even low-severity vulnerabilities seriously. Exposure of authentication tokens could lead to compliance issues, reputational damage, and potential lateral movement within the network if combined with other vulnerabilities or misconfigurations. The risk is heightened in environments where network traffic is not fully encrypted or where internal network segmentation is weak, allowing attackers to sniff traffic. However, since no known exploits are reported and exploitation complexity is high, the immediate threat level is low but should not be ignored.

CWE-319Cleartext Transmission of Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Architecture and Design
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
Implementation
When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Implementation
When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
V1.9.1 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Harvesting Information via API Event Monitoring (opens in a new tab)
Signature Spoofing by Mixing Signed and Unsigned Content (opens in a new tab)
Sniff Application Code (opens in a new tab)
Interception (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0122368 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Aug 2025, 01:01 UTC

WeaknessesCWE-319

Technical details

References

Community reviews

Related threats