dbcve.org
AionApplication · Hcltech

CVE-2025-52632

HIGH · 7.5 CVSS v3.1 Published 2025-10-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Missing Secure Attribute in Encrypted Session (SSL) Cookie vulnerability in HCL AION.This issue affects AION: 2.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HCL AION 2.0 fails to set the Secure flag on encrypted session (SSL) cookies, allowing these cookies to be transmitted over unencrypted HTTP connections. This could enable cookie theft via network interception in mixed SSL/TLS environments.

MitigationConfigure the session cookie to include the Secure attribute, ensuring it is only transmitted over HTTPS connections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AionApplication
Affected:= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed HCL AION version
    Check the installed version of HCL AION in your environment (typically via application metadata, About screen, or version file). Compare against the affected version 2.0.0.
    Affected if The installed version is exactly 2.0.0.
  2. Confirm application uses session cookies
    Monitor HTTP responses from the HCL AION application using browser developer tools or a network proxy. Look for Set-Cookie headers in responses.
    Affected if The application sets session cookies (JSESSIONID or similar) in HTTP responses.
  3. Inspect cookie Secure flag
    Examine the Set-Cookie header(s) for the session cookie. Check whether the Secure attribute is present in the cookie definition.
    Affected if The session cookie is set WITHOUT the Secure attribute (no 'Secure' flag in the Set-Cookie header).
  4. Verify mixed SSL/TLS environment
    Check if the application is accessible over both HTTP (port 80) and HTTPS (port 443), or if there are any links pointing to HTTP URLs within the application.
    Affected if The application is accessible over unencrypted HTTP while also supporting HTTPS.

You are affected if HCL AION version 2.0.0 is running and the session cookie lacks the Secure flag, particularly if the application handles sensitive data in a mixed HTTP/HTTPS environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure the session cookie to include the Secure attribute, ensuring it is only transmitted over HTTPS connections.

Fix this in Aion Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52632 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52632 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data