# CVE-2021-3644: wildfly-core allows user with access to management interface to access vault expression, retrieve item from vault

> An authenticated user with management access can retrieve unauthorized vault secrets, compromising data confidentiality and integrity in WildFly.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** BIT-wildfly-2021-3644, GHSA-w88m-2936-rmxr

## What is CVE-2021-3644?

CVE-2021-3644 is a low-severity vulnerability in wildfly-core, published on 26 Aug 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in wildfly-core in all versions. If a vault expression is in the form of a single attribute that contains multiple expressions, a user who was granted access to the management interface can potentially access a vault expression they should not be able to access and possibly retrieve the item which was stored in the vault. The highest threat from this vulnerability is data confidentiality and integrity.

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

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

5 open source packages ship an affected version, including org.wildfly.core:wildfly-server and wildfly. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.wildfly.core:wildfly-server` | Maven | All versions | 16.0.1.Final |
| `org.wildfly.core:wildfly-server` | Maven | All versions | 16.0.1.Final |
| `org.wildfly.core:wildfly-server` | Maven | From 17.0.0.Beta2 | 17.0.0.Beta3 |
| `org.wildfly.core:wildfly-server` | Maven | From 17.0.0.Beta2 | 17.0.0.Beta3 |
| `wildfly` | Bitnami | From 16.0.0 | 16.0.1 |

Products: Redhat Descision Manager, Redhat Wildfly.

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

Upgrade org.wildfly.core:wildfly-server to a fixed version for your release line: 16.0.1.Final or 17.0.0.Beta3.

## Is CVE-2021-3644 being exploited?

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

## Other vulnerabilities in wildfly-core

- [CVE-2022-0853](https://insights.sbomify.com/CVE-2022-0853/): Information disclosure in jboss-client (high 7.5)
- [CVE-2021-20306](https://insights.sbomify.com/CVE-2021-20306/): Information disclosure in Business-central (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-3644 is a low-severity vulnerability in wildfly-core, published on 26 Aug 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-3644 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.wildfly.core:wildfly-server (Maven): affected all versions; fixed in 16.0.1.Final
- org.wildfly.core:wildfly-server (Maven): affected all versions; fixed in 16.0.1.Final
- org.wildfly.core:wildfly-server (Maven): affected from 17.0.0.Beta2; fixed in 17.0.0.Beta3
- org.wildfly.core:wildfly-server (Maven): affected from 17.0.0.Beta2; fixed in 17.0.0.Beta3
- wildfly (Bitnami): affected from 16.0.0; fixed in 16.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-2021-3644/ (Markdown: https://insights.sbomify.com/CVE-2021-3644/index.md)
```

## Sources

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

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