# CVE-2024-4029: Wildfly: no timeout for eap management interface may lead to denial of service (dos)

> Attackers can exhaust file descriptors on the Wildfly management interface, causing a denial of service due to missing connection limits.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 May 2024
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-x7g6-rwhc-g7mj

## What is CVE-2024-4029?

CVE-2024-4029 is a medium-severity denial of service vulnerability in Red Hat Build of Keycloak, published on 2 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in Wildfly’s management interface. Due to the lack of limitation of sockets for the management interface, it may be possible to cause a denial of service hitting the nofile limit as there is no possibility to configure or set a maximum number of connections.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

2 open source packages ship an affected version, including org.wildfly:wildfly-domain-http.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.wildfly:wildfly-domain-http` | Maven | All versions to 24.0.0.Final | None |
| `org.wildfly:wildfly-domain-http` | Maven | All versions to 24.0.0.Final | None |

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

Apply the vendor's patch.

## Is CVE-2024-4029 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4029 is a medium-severity denial of service vulnerability in Red Hat Build of Keycloak, published on 2 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4029 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.wildfly:wildfly-domain-http (Maven): affected all versions up to 24.0.0.Final; no fix listed
- org.wildfly:wildfly-domain-http (Maven): affected all versions up to 24.0.0.Final; no fix listed

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

## Sources

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

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