HCL AION CVE-2025-62314

Exploitation requires the attacker to occupy an adjacent network position to the HCL AION deployment (AV:A) - open-internet attacks are not possible without a prior network foothold or VPN-equivalent access. The attacker must hold at least low-privileged AION credentials (PR:L), and user interaction is indicated as required by the CVSS vector (UI:R), though the specific nature of that interaction is not described in the vendor advisory. High attack complexity (AC:H) further limits opportunistic exploitation, suggesting that conditions favorable to the attack are not consistently present. The specific endpoints lacking anti-automation controls are not named in the advisory, requiring reconnaissance to identify them. Exploitation is further bounded to AION v2.1.0 deployments where affected endpoints are reachable from the attacker's network segment without intervening WAF, reverse proxy throttling, or network ACL controls.

The vendor-assigned CVSS score of 5.6 (Medium) is broadly consistent with the constraint-heavy vector: adjacent network access (AV:A), high attack complexity (AC:H), low-privilege credential requirement (PR:L), and mandatory user interaction (UI:R) collectively narrow the window for opportunistic exploitation. The High availability impact (A:H) suggests that successful automated flooding could cause meaningful service disruption, while confidentiality and integrity impacts are limited (C:L, I:L). No EPSS data was included in the intelligence feed, and the absence of a KEV listing or public POC places this squarely in the monitor-and-patch tier rather than emergency response. Even a mid-sized municipal IT team in olsztyn running an AION deployment would find the adjacent-network constraint a meaningful practical barrier, since exploitation demands a foothold within the same network segment rather than open-internet access. The AC:H rating merits scrutiny - if targeted endpoints are routinely accessible and standard automation frameworks apply to the endpoint type, real-world attack complexity may be lower than the vendor-assigned score implies, though this cannot be confirmed from the data provided. The UI:R metric is unusual for an automation-based attack class and may represent a specific workflow dependency not fully described in the advisory.

An attacker holding low-privileged AION credentials and positioned on the same network segment as the target deployment scripts automated requests against endpoints lacking rate limiting, submitting high volumes without triggering defensive countermeasures. Depending on the endpoint type, this enables credential enumeration, data harvesting through information-disclosure responses, or service disruption through request flooding. No public exploit code has been identified, so exploitation currently requires custom scripting and knowledge of the specific vulnerable endpoints.