# CVE-2024-30152: HCL SX is affected by usage of a weak cryptographic algorithm

> Weak cryptographic algorithm in HCL SX allows attackers to access sensitive information or modify data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Apr 2025
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-xv35-w389-wr74

## What is CVE-2024-30152?

CVE-2024-30152 is a medium-severity vulnerability in HCL SX, published on 25 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

HCL SX v21 is affected by usage of a weak cryptographic algorithm.  An attacker could exploit this weakness to gain access to sensitive information, modify data, or other impacts.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2024-30152?

It affects 1 product.


Products: Hcltech Hcl Sx.

## How do I fix CVE-2024-30152?

No fix has been published for CVE-2024-30152 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-30152 being exploited?

There is no known exploitation of CVE-2024-30152 in the wild and no public exploit code.

## Other vulnerabilities in HCL SX

- [CVE-2024-30155](https://insights.sbomify.com/CVE-2024-30155/): HCL SX is susceptible to cookie with Insecure, Improper, or Missing SameSite attribute vulnerability (medium 5.5)
- [CVE-2024-30154](https://insights.sbomify.com/CVE-2024-30154/): HCL SX is susceptible to a Cross-Site Request Forgery (CSRF) vulnerability (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30152 and fix it if it is affected.

What it is: CVE-2024-30152 is a medium-severity vulnerability in HCL SX, published on 25 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-30152 in the wild and no public exploit code.

Affected product: HCL SX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-30152/ (Markdown: https://insights.sbomify.com/CVE-2024-30152/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-30152
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-30152
- OSV: https://osv.dev/vulnerability/CVE-2024-30152

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-30152/
Summaries are generated and may contain mistakes; the official description above is the record.