# CVE-2024-8447: Narayana: deadlock via multiple join requests sent to lra coordinator

> An attacker can cause a denial of service in the Narayana LRA Coordinator by sending concurrent join requests during a cancellation operation.

- **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:** 2 Jan 2025
- **Updated:** 7 Sep 2026
- **Also known as:** GHSA-qq9f-q439-2574

## What is CVE-2024-8447?

CVE-2024-8447 is a medium-severity denial of service vulnerability in Red Hat JBoss Data Grid 7, published on 2 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security issue was discovered in the LRA Coordinator component of Narayana. When Cancel is called in LRA, an execution time of approximately 2 seconds occurs. If Join is called with the same LRA ID within that timeframe, the application may crash or hang indefinitely, leading to a denial of service.

Weakness: CWE-833 (Deadlock)

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

2 open source packages ship an affected version, including org.jboss.narayana.rts:lra-coordinator-jar.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jboss.narayana.rts:lra-coordinator-jar` | Maven | All versions | 7.1.0.Final |
| `org.jboss.narayana.rts:lra-coordinator-jar` | Maven | All versions | 7.1.0.Final |

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

Upgrade org.jboss.narayana.rts:lra-coordinator-jar to 7.1.0.Final or later.

## Is CVE-2024-8447 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8447 is a medium-severity denial of service vulnerability in Red Hat JBoss Data Grid 7, published on 2 Jan 2025. 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-8447 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jboss.narayana.rts:lra-coordinator-jar (Maven): affected all versions; fixed in 7.1.0.Final
- org.jboss.narayana.rts:lra-coordinator-jar (Maven): affected all versions; fixed in 7.1.0.Final

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-8447/ (Markdown: https://insights.sbomify.com/CVE-2024-8447/index.md)
```

## Sources

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

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