Vulnerability in HCL AION (CVE-2025-62315)
Summary
Vulnerability in HCL AION (CVE-2025-62315). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
HCL AION is affected by a vulnerability where certain input fields do not enforce sufficient server-side input validation. Unexpected or crafted input may be accepted by the application, potentially resulting in unintended behavior or security impact under certain conditions.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-62315 has been found in HCL AION.
Risk of unauthorized operations or information disclosure. CVSS score: 3.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "HCL AION CVE-2025-62315" on the vendor's site.
CVE-2025-62315 (HCL AION) — CWE-116 / CVSS v3 3.4
Attack vector: adjacent-network
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-116) exists in HCL AION.
Check the vendor advisory for the affected versions of HCL AION.
Severity: Low (CVSS 3.4/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで HCL AION を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web psirt@hcl.com
- web nvd.nist.gov
- web github.com