CVE-2025-52611: HCL iControl was affected by Unhandled Exception - Stack Trace Disclosure vulnerability
HCL iControl v4.0.0 was affected by Unhandled Exception - Stack Trace Disclosure vulnerability. The error occurs due to an undefined property being accessed in the application's JavaScript code. Specifically, the code attempts to read the property dashboard key from an object that is undefined. This issue likely stems from one of the following: A missing or improperly initialized object.
Security readout for executives and security teams
Plain-English summary
This is a low-severity information disclosure issue in HCL iControl 4.0.0. A JavaScript error can expose stack trace details when the application tries to read a dashboard key from an undefined object. The main business risk is leakage of implementation details that could help later reconnaissance, not direct system takeover.
Executive priority
Treat as routine remediation unless HCL iControl is broadly exposed or used by many privileged users. Prioritize confirming affected version presence and applying vendor guidance through normal patch management.
Technical view
CVE-2025-52611 maps to CWE-209. The CVSS 3.1 vector is AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N, meaning network reachable, high complexity, low privileges required, and confidentiality impact only. The source bundle identifies HCL iControl 4.0.0 as affected and default status as unaffected for other versions.
Likely exposure
Exposure appears limited to environments running HCL iControl 4.0.0. The CVSS vector indicates an attacker needs low privileges and the issue is high complexity. Systems not running this version are not identified as affected in the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. The disclosed impact is limited stack trace exposure, which may reveal internal implementation details but does not indicate integrity or availability compromise.
Researcher notes
Evidence is narrow: affected product, version, CWE, CVSS vector, and one HCL reference. The bundle does not include exploit details, active exploitation evidence, or explicit patch status. Avoid expanding affected scope beyond HCL iControl 4.0.0.
Mitigation direction
Review HCL advisory KB0131041 for vendor-approved remediation guidance.
Upgrade or apply a vendor fix if HCL provides one for iControl 4.0.0.
Restrict iControl access to trusted users and management networks.
Reduce verbose error exposure in production where supported by vendor configuration.
Validation and detection
Inventory HCL iControl deployments and confirm installed versions.
Identify any running HCL iControl 4.0.0 instances.
Review application logs for dashboard key undefined-object errors.
Confirm production error pages do not expose stack traces to users.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-209: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-209 · source CWE mapping
Generation of Error Message Containing Sensitive Information
Generation of Error Message Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.