# CVE-2021-20250: JBoss EJB Client information disclosure vulnerability

> Attackers can access privileged JBoss EJB client actions to disclose sensitive server information, affecting WildFly deployments.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 13 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2259-h742-5vr4

## What is CVE-2021-20250?

CVE-2021-20250 is a medium-severity vulnerability in wildfly, published on 13 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in wildfly. The JBoss EJB client has publicly accessible privileged actions which may lead to information disclosure on the server it is deployed on. The highest threat from this vulnerability is to data confidentiality.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2021-20250?

2 open source packages ship an affected version, including org.jboss:jboss-ejb-client. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jboss:jboss-ejb-client` | Maven | All versions | 4.0.39 |
| `org.jboss:jboss-ejb-client` | Maven | All versions | 4.0.39 |

Products: Redhat Jboss-Ejb-Client, Redhat Jboss Enterprise Application Platform Expansion Pack.

## How do I fix CVE-2021-20250?

Upgrade org.jboss:jboss-ejb-client to 4.0.39 or later.

## Is CVE-2021-20250 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-20250 and fix it if it is affected.

What it is: CVE-2021-20250 is a medium-severity vulnerability in wildfly, published on 13 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-20250 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jboss:jboss-ejb-client (Maven): affected all versions; fixed in 4.0.39
- org.jboss:jboss-ejb-client (Maven): affected all versions; fixed in 4.0.39

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

## Sources

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

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