dbcve.org
QuarkusApplication

CVE-2022-4147

HIGH · 7.5 CVSS v3.1 Published 2022-12-06
Fix available
A fix is available. Upgrade to 2.13.5 / 2.14.2 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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
Quarkus CORS filter allows simple GET and POST requests with invalid Origin to proceed. Simple GET or POST requests made with XMLHttpRequest are the ones which have no event listeners registered on the object returned by the XMLHttpRequest upload property and have no ReadableStream object used in the request.

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 · high confidence

The Quarkus CORS filter incorrectly processes simple GET and POST requests (XMLHttpRequest without upload event listeners or ReadableStream) and allows them to proceed with invalid Origin headers, bypassing CORS security restrictions and enabling potential cross-origin attacks.

MitigationUpdate Quarkus to a patched version that properly validates Origin headers for all simple requests; audit existing deployments for unauthorized cross-origin access.

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
QuarkusApplication
Affected:>= 2.0, < 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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 installed Quarkus version
    Check your project build file (pom.xml for Maven or build.gradle for Gradle) for the quarkus-bom or individual Quarkus dependency versions, or run 'quarkus --version' if using the CLI
    Affected if The version falls within >= 2.0.0 and < 2.13.5, OR >= 2.14.0 and < 2.14.2
  2. Verify CORS is enabled in your application
    Check your application.properties or application.yaml for any 'quarkus.http.cors' configuration properties, or look for @org.eclipse.microprofile.config.inject.ConfigProperty with 'cors' in the name, or check for CORS-related code using the CORS filter
    Affected if CORS is enabled and the Quarkus version is in the affected range
  3. Inspect CORS origin configuration
    Examine the 'quarkus.http.cors.origins' or 'quarkus.http.cors.access-control-allow-origin' setting in your configuration file to see which origins are permitted
    Affected if CORS is configured with origins that could allow bypassing validation (the vulnerability allows invalid Origin headers to bypass checks)
  4. Confirm simple request handling
    Review any XMLHttpRequest or fetch() calls in your frontend code that make GET or POST requests without custom headers, upload event listeners, or ReadableStream - these are the 'simple' request types affected by this vulnerability
    Affected if Your application uses such simple cross-origin requests and uses a Quarkus version in the affected range

Your environment is affected if you are running a Quarkus version in the vulnerable range (2.0.0 to 2.13.4 or 2.14.0 to 2.14.1) and have CORS enabled, because the filter will incorrectly allow simple GET/POST requests with invalid Origin headers to bypass security restrictions.

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

Update Quarkus to a patched version that properly validates Origin headers for all simple requests; audit existing deployments for unauthorized cross-origin access.

Recommended fix High confidence

2.14.2.Final or later (or 2.13.5.Final if staying on 2.13.x branch)

  1. Update the Quarkus version in your pom.xml or build.gradle file
  2. Change the quarkus-bom version to 2.14.2.Final or later (e.g., <version>2.14.2.Final</version>)
  3. Run a build to verify the dependency resolves correctly
  4. Test your application's CORS behavior to confirm the fix is applied
  5. Alternatively, if staying on the 2.13.x line, upgrade to 2.13.5.Final or later
Caveat Review Quarkus 2.14 release notes for any breaking changes between your current version and the target version

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

Fix this in Quarkus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
5.0 hours of engineering $880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-4147 — 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-4147 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