# CVE-2024-27267: IBM SDK, Java Technology Edition denial of service

> A race condition in the IBM Java SDK ORB allows remote attackers to cause a denial of service.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Aug 2024
- **Updated:** 29 Sep 2025
- **Also known as:** GHSA-7p73-rpm9-rwr6, RHSA-2024:6595

## What is CVE-2024-27267?

CVE-2024-27267 is a medium-severity vulnerability in IBM SDK, Java Technology Edition, published on 14 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Object Request Broker (ORB) in IBM SDK, Java Technology Edition 7.1.0.0 through 7.1.5.18 and 8.0.0.0 through 8.0.8.26 is vulnerable to remote denial of service, caused by a race condition in the management of ORB listener threads.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `java-1.8.0-ibm` | Red Hat:enterprise_linux:8::supplementary | All versions | 1:1.8.0.8.30-2.el8_10 |
| `java-1.8.0-ibm-demo` | Red Hat:enterprise_linux:8::supplementary | All versions | 1:1.8.0.8.30-2.el8_10 |
| `java-1.8.0-ibm-devel` | Red Hat:enterprise_linux:8::supplementary | All versions | 1:1.8.0.8.30-2.el8_10 |
| `java-1.8.0-ibm-headless` | Red Hat:enterprise_linux:8::supplementary | All versions | 1:1.8.0.8.30-2.el8_10 |
| `java-1.8.0-ibm-jdbc` | Red Hat:enterprise_linux:8::supplementary | All versions | 1:1.8.0.8.30-2.el8_10 |
| `java-1.8.0-ibm-plugin` | Red Hat:enterprise_linux:8::supplementary | All versions | 1:1.8.0.8.30-2.el8_10 |
| `java-1.8.0-ibm-src` | Red Hat:enterprise_linux:8::supplementary | All versions | 1:1.8.0.8.30-2.el8_10 |
| `java-1.8.0-ibm-webstart` | Red Hat:enterprise_linux:8::supplementary | All versions | 1:1.8.0.8.30-2.el8_10 |

Products: Ibm Java Sdk.

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

Apply the vendor's patch.

## Is CVE-2024-27267 being exploited?

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

## Other vulnerabilities in IBM SDK, Java Technology Edition

- [CVE-2014-8891](https://insights.sbomify.com/CVE-2014-8891/): Security feature bypass in n/a (critical 10.0)
- [CVE-2015-5041](https://insights.sbomify.com/CVE-2015-5041/): Information disclosure in n/a (critical 9.1)
- [CVE-2018-1417](https://insights.sbomify.com/CVE-2018-1417/): Privilege escalation in SDK, Java Technology Edition (high 8.1)
- [CVE-2016-0363](https://insights.sbomify.com/CVE-2016-0363/): Security feature bypass in n/a (high 8.1)
- [CVE-2016-0376](https://insights.sbomify.com/CVE-2016-0376/): Deserialization in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-27267 is a medium-severity vulnerability in IBM SDK, Java Technology Edition, published on 14 Aug 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-27267 in the wild and no public exploit code.

Affected product: IBM SDK, Java Technology Edition. 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-27267/ (Markdown: https://insights.sbomify.com/CVE-2024-27267/index.md)
```

## Sources

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

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