dbcve.org
Build Of QuarkusApplication · Redhat

CVE-2022-4116

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-22
Fix available
A fix is available. Upgrade to 2.13.5 / 2.14.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A drive-by localhost attack vulnerability exists in Quarkus's Dev UI Config Editor. By tricking a user into visiting a malicious page while accessing the Dev UI, attackers can potentially execute arbitrary code remotely through the Config Editor component.

MitigationUpgrade to a patched version of Quarkus that addresses CVE-2022-4116. If immediate patching is not possible, restrict access to the Dev UI or disable it in production environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of QuarkusApplication
Affected:all versions
QuarkusApplication
Affected:< 2.13.5>= 2.14.0, < 2.14.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Quarkus version
    Inspect your project build file (pom.xml or build.gradle) for the Quarkus version, or check the quarkus-core JAR manifest. Also run 'quarkus --version' if Quarkus CLI is installed.
    Affected if The version is < 2.13.5, or >= 2.14.0 but < 2.14.2, or if you use Redhat Build of Quarkus (all versions)
  2. Confirm Dev UI is accessible
    Check if your application exposes the /q/dev endpoint. This is typically available when running in dev mode (./mvnw quarkus:dev) or in test mode. Verify if the Dev UI is reachable in your environment.
    Affected if Dev UI endpoint is accessible without authentication in dev or test mode
  3. Verify Config Editor component status
    Access the Dev UI at /q/dev and navigate to the Config Editor page. Check if the component loads and accepts input for configuration editing.
    Affected if The Config Editor is loaded and functional within the Dev UI interface
  4. Check Dev UI production exposure
    Review your deployment configuration to determine if Dev UI endpoints (including Config Editor) are inadvertently exposed in production builds or non-dev profiles.
    Affected if Dev UI is accessible in production or outside trusted network boundaries

You are affected if your Quarkus version falls within the vulnerable ranges AND the Dev UI Config Editor is accessible in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.13.5 / 2.14.2 or later
Fixed in 2.13.52.14.2
Interim mitigation

Upgrade to a patched version of Quarkus that addresses CVE-2022-4116. If immediate patching is not possible, restrict access to the Dev UI or disable it in production environments.

Recommended fix High confidence

2.13.5 or 2.14.2 (minimum fixed versions)

  1. Identify your current Quarkus version by checking your pom.xml or gradle build file
  2. If using Quarkus 2.13.x, upgrade to version 2.13.5 or later
  3. If using Quarkus 2.14.0-2.14.1, upgrade to version 2.14.2 or later
  4. Alternatively, upgrade to the latest stable release in your minor branch (e.g., 2.13.x or 2.14.x)
  5. After upgrading, rebuild and test your application to ensure the Dev UI functions correctly
Caveat Patch releases (2.13.5, 2.14.2) typically have minimal breaking changes; review Quarkus release notes for any migration notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Build Of Quarkus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-4116 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-4116 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data