# CVE-2024-22361: IBM Semeru Runtime information disclosure

> Weak cryptographic algorithms in IBM Semeru Runtime allow attackers to decrypt highly sensitive information.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2024
- **Updated:** 19 Aug 2024
- **Also known as:** GHSA-r7j8-523f-fpxp

## What is CVE-2024-22361?

CVE-2024-22361 is a medium-severity vulnerability in IBM Semeru Runtime, published on 10 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Semeru Runtime 8.0.302.0 through 8.0.392.0, 11.0.12.0 through 11.0.21.0, 17.0.1.0 - 17.0.9.0, and 21.0.1.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.  IBM X-Force ID:  281222.

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

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

It affects 1 product.


Products: Ibm Semeru Runtime.

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

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

## Is CVE-2024-22361 being exploited?

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

## Other vulnerabilities in IBM Semeru Runtime

- [CVE-2025-2900](https://insights.sbomify.com/CVE-2025-2900/): IBM Semeru Runtime denial of service (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22361 is a medium-severity vulnerability in IBM Semeru Runtime, published on 10 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22361 in the wild and no public exploit code.

Affected product: IBM Semeru Runtime. 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-22361/ (Markdown: https://insights.sbomify.com/CVE-2024-22361/index.md)
```

## Sources

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

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