# CVE-2020-25724: Unsynchronized Access to Shared Data in a Multithreaded Context in RESTEasy

> An attacker can exploit incorrect HTTP responses in RESTEasy to access privileged information, compromising confidentiality and integrity.

- **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:** 26 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9699-gm7f-cmjv

## What is CVE-2020-25724?

CVE-2020-25724 is a medium-severity vulnerability in resteasy, published on 26 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 RESTEasy, where an incorrect response to an HTTP request is provided. This flaw allows an attacker to gain access to privileged information. The highest threat from this vulnerability is to confidentiality and integrity. Versions before resteasy 2.0.0.Alpha3 are affected.

Weakness: CWE-567 (Unsynchronized Access to Shared Data in a Multithreaded Context)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jboss.resteasy:resteasy-bom` | Maven | All versions | 2.0-beta-2 |
| `org.jboss.resteasy:resteasy-bom` | Maven | All versions | 2.0-beta-2 |

Products: Quarkus Quarkus, Redhat Resteasy.

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

Upgrade org.jboss.resteasy:resteasy-bom to 2.0-beta-2 or later.

## Is CVE-2020-25724 being exploited?

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

## Other vulnerabilities in resteasy

- [CVE-2022-4116](https://insights.sbomify.com/CVE-2022-4116/): Code injection in quarkus dev ui config editor (critical 9.8)
- [CVE-2022-2466](https://insights.sbomify.com/CVE-2022-2466/): Quarkus does not terminate HTTP requests header context (critical 9.8)
- [CVE-2024-12225](https://insights.sbomify.com/CVE-2024-12225/): Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass (critical 9.1)
- [CVE-2026-39852](https://insights.sbomify.com/CVE-2026-39852/): Quarkus authorization bypass via semicolon path normalization inconsistency (high 8.8)
- [CVE-2022-0981](https://insights.sbomify.com/CVE-2022-0981/): Privilege escalation in quarkus (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25724 is a medium-severity vulnerability in resteasy, published on 26 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-2020-25724 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jboss.resteasy:resteasy-bom (Maven): affected all versions; fixed in 2.0-beta-2
- org.jboss.resteasy:resteasy-bom (Maven): affected all versions; fixed in 2.0-beta-2

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

## Sources

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

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