# CVE-2022-4116: Code injection in quarkus dev ui config editor

> Attackers can achieve remote code execution via drive-by localhost attacks on the Quarkus Dev UI Config Editor.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-g56w-cwg4-hxx9

## What is CVE-2022-4116?

CVE-2022-4116 is a critical vulnerability in quarkus, published on 22 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in quarkus. This security flaw happens in Dev UI Config Editor which is vulnerable to drive-by localhost attacks leading to remote code execution.

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

4 open source packages ship an affected version, including io.quarkus:quarkus-vertx-http-deployment. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.quarkus:quarkus-vertx-http-deployment` | Maven | All versions | 2.13.5.Final |
| `io.quarkus:quarkus-vertx-http-deployment` | Maven | All versions | 2.13.5.Final |
| `io.quarkus:quarkus-vertx-http-deployment` | Maven | From 2.14.0 | 2.14.2.Final |
| `io.quarkus:quarkus-vertx-http-deployment` | Maven | From 2.14.0 | 2.14.2.Final |

Products: Quarkus Quarkus, Redhat Build of Quarkus.

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

Upgrade io.quarkus:quarkus-vertx-http-deployment to a fixed version for your release line: 2.13.5.Final or 2.14.2.Final.

## Is CVE-2022-4116 being exploited?

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

## Other vulnerabilities in quarkus

- [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)
- [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-4116 and fix it if it is affected.

What it is: CVE-2022-4116 is a critical vulnerability in quarkus, published on 22 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4116 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.quarkus:quarkus-vertx-http-deployment (Maven): affected all versions; fixed in 2.13.5.Final
- io.quarkus:quarkus-vertx-http-deployment (Maven): affected all versions; fixed in 2.13.5.Final
- io.quarkus:quarkus-vertx-http-deployment (Maven): affected from 2.14.0; fixed in 2.14.2.Final
- io.quarkus:quarkus-vertx-http-deployment (Maven): affected from 2.14.0; fixed in 2.14.2.Final

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

## Sources

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

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