# CVE-2020-25689: Uncontrolled Resource Consumption in WildFly

> An attacker can cause a denial of service by triggering a memory leak in WildFly's host-controller reconnection logic.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-wildfly-2020-25689, GHSA-97hp-6q9g-5cw2

## What is CVE-2020-25689?

CVE-2020-25689 is a medium-severity denial of service vulnerability in Netapp Active Iq Unified Manager, published on 30 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A memory leak flaw was found in WildFly in all versions up to 21.0.0.Final, where host-controller tries to reconnect in a loop, generating new connections which are not properly closed while not able to connect to domain-controller. This flaw allows an attacker to cause an Out of memory (OOM) issue, leading to a denial of service. The highest threat from this vulnerability is to system availability.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2020-25689?

3 open source packages ship an affected version, including org.wildfly:wildfly-dist and wildfly. It affects 10 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.wildfly:wildfly-dist` | Maven | All versions | 21.0.1 |
| `org.wildfly:wildfly-dist` | Maven | All versions | 21.0.1 |
| `wildfly` | Bitnami | All versions | 21.0.1 |

Products: Netapp Active Iq Unified Manager, Netapp Oncommand Insight, Netapp Service Level Manager, Redhat Fuse, Redhat Jboss Data Grid, Redhat Jboss Enterprise Application Platform, Redhat Jboss Fuse, Redhat Openshift Application Runtimes, Redhat Single Sign-On, Redhat Wildfly.

## How do I fix CVE-2020-25689?

Upgrade org.wildfly:wildfly-dist to 21.0.1 or later.

## Is CVE-2020-25689 being exploited?

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

## Other vulnerabilities in Netapp Active Iq Unified Manager

- [CVE-2022-31692](https://insights.sbomify.com/CVE-2022-31692/): Spring Security authorization rules can be bypassed via forward or include dispatcher types (critical 9.8)
- [CVE-2022-2526](https://insights.sbomify.com/CVE-2022-2526/): Use after free in systemd-resolved (critical 9.8)
- [CVE-2022-22978](https://insights.sbomify.com/CVE-2022-22978/): Authorization bypass in Spring Security (critical 9.8)
- [CVE-2021-22931](https://insights.sbomify.com/CVE-2021-22931/): Code injection in Node (critical 9.8)
- [CVE-2018-2938](https://insights.sbomify.com/CVE-2018-2938/): Code injection in Java (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25689 and fix it if it is affected.

What it is: CVE-2020-25689 is a medium-severity denial of service vulnerability in Netapp Active Iq Unified Manager, published on 30 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25689 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.wildfly:wildfly-dist (Maven): affected all versions; fixed in 21.0.1
- org.wildfly:wildfly-dist (Maven): affected all versions; fixed in 21.0.1
- wildfly (Bitnami): affected all versions; fixed in 21.0.1

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

## Sources

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

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