# CVE-2022-0981: Privilege escalation in quarkus

> A flaw in Quarkus RestEasy Reactive allows state leakage between requests, enabling low-privileged users to perform database operations with unintended higher privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** No
- **Published:** 23 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-wr4r-g543-785x

## What is CVE-2022-0981?

CVE-2022-0981 is a high-severity vulnerability in quarkus, published on 23 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in Quarkus. The state and potentially associated permissions can leak from one web request to another in RestEasy Reactive. This flaw allows a low-privileged user to perform operations on the database with a different set of privileges than intended.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2022-0981?

It affects 1 product.


Products: Quarkus Quarkus.

## How do I fix CVE-2022-0981?

No fix has been published for CVE-2022-0981 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-0981 being exploited?

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

## Other vulnerabilities in quarkus

- [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-2023-6267](https://insights.sbomify.com/CVE-2023-6267/): Quarkus: json payload getting processed prior to security checks when rest resources are used with annotations. (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0981 and fix it if it is affected.

What it is: CVE-2022-0981 is a high-severity vulnerability in quarkus, published on 23 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0981 in the wild and no public exploit code.

Affected product: quarkus. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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