Cross-origin request acceptance via invalid Origin handling
Published Dec 6, 2022 · Updated Apr 14, 2025
Improper authorization in Red Hat Quarkus 2 allows remote attackers to issue cross-origin GET or POST requests through the CORS filter. The Vert.x HTTP CORS filter returns 200 OK and passes simple XMLHttpRequest traffic to application handlers when the Origin value is not allowed. Exploitation requires CORS to be enabled, user interaction with attacker-controlled content, and a target endpoint whose response or state has security significance.
Summary
What happened
Improper authorization in Red Hat Quarkus 2 allows remote attackers to issue cross-origin GET or POST requests through the CORS filter. The Vert.x HTTP CORS filter returns 200 OK and passes simple XMLHttpRequest traffic to application handlers when the Origin value is not allowed. Exploitation requires CORS to be enabled, user interaction with attacker-controlled content, and a target endpoint whose response or state has security significance.
The record
- CVE
- CVE-2022-4147
- Published
- Dec 6, 2022
- Updated
- Apr 14, 2025
- Vendor
- Red Hat
- Product
- Quarkus
- Classifications
- CWE-285, CWE-1026, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 6, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo