Description

HCL AION is affected by a missing encryption vulnerability in the WebSocket connection set up by the GenAI web interface. The connection used the unencrypted WebSocket protocol (ws://localhost:8000) instead of an encrypted (wss://) channel. This may allow data exchanged over the connection to be intercepted or read by an attacker on the network, potentially resulting in unintended behavior or security impact under certain conditions.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "3.7",
  "pubDate": "2026-11-06T14:17:11.183Z",
  "pubdate": "2026-11-06T14:17:11.183Z",
  "executiveSummary": "HCL AION is vulnerable to cleartext communication exposure due to the implementation of an insecure WebSocket protocol (ws://) within its GenAI web interface.\nThis vulnerability allows for the interception of sensitive data transmitted between the client and the application server.\nBy utilizing unencrypted channels instead of the secure WebSocket (wss://) protocol, the application fails to provide necessary transit-layer encryption, leaving data vulnerable to man-in-the-middle (MitM) attacks.\nThe risk implication involves unauthorized information disclosure, as an attacker positioned on the local network or through upstream traffic observation could read, capture, or potentially manipulate the data stream.\nExploitation does not require authentication, but it does require the attacker to have network-level proximity or access to intercept the traffic passing between the client and the localhost:8000 endpoint.\nThis represents a failure in transport security controls, undermining the confidentiality and integrity of the GenAI interface sessions.",
  "technicalDetails": "The vulnerability originates from the HCL AION GenAI web interface's configuration, which mandates the use of the ws:// protocol over TCP port 8000 for its real-time WebSocket communications.\nUnlike the wss:// protocol, which leverages TLS (Transport Layer Security) to encrypt the WebSocket payload, the ws:// protocol transmits frames as plaintext. This omission of a cryptographic layer exposes the entire WebSocket handshake and subsequent data frames to network sniffing.\nThe attack flow commences when a user initiates a connection to the GenAI interface. Because the application defaults to an unencrypted channel, any intermediary device or malicious actor with access to the local network architecture can perform packet capture or traffic redirection.\nThe root cause is an insecure hardcoded connection string targeting localhost:8000 without enforcing SSL/TLS wrapping. While the target is specified as localhost, in scenarios where the interface is exposed or reachable via network-bridging, the lack of encryption ensures that data visibility is not restricted to the local host's loopback interface.\nDuring exploitation, an attacker performs an ARP spoofing or DNS poisoning attack to intercept the traffic stream. Because no encryption is present, the attacker can use tools like Wireshark or tcpdump to reconstruct the WebSocket frames in real-time. This includes potentially sensitive prompt data, model outputs, or session-related metadata transmitted during the interactive GenAI session.\nThe absence of a wss:// implementation means there is no verification of server identity, leaving the user susceptible to malicious proxying. Once the traffic is intercepted, the impact extends beyond mere eavesdropping; an attacker could inject malicious frames into the communication stream, potentially influencing the client-side rendering of the GenAI response or triggering client-side logic flaws via manipulated data payloads.\nThe vulnerability resides within the WebSocket connection initialization logic of the GenAI web interface component. No specific privilege is required to perform the interception, as the primary constraint is simply the ability to observe the unencrypted network traffic flowing to the service endpoint."
}