CVE-2023-6267 — resteasy-reactive
HIGHCVE-2023-6267 is a high-severity (CVSS 8.6) CWE-755 vulnerability in io.quarkus.resteasy.reactive:resteasy-reactive. A fix is available for io.quarkus.resteasy.reactive:resteasy-reactive — see the affected versions and patch details below.
Quarkus: json payload getting processed prior to security checks when rest resources are used with annotations.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-6267.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.quarkus.resteasy.reactive:resteasy-reactive☕io.quarkus.resteasy.reactive:resteasy-reactiveReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A flaw was found in the json payload. If annotation based security is used to secure a REST resource, the JSON body that the resource may consume is being processed (deserialized) prior to the security constraints being evaluated and applied. This does not happen with configuration based security.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkus.resteasy.reactive:resteasy-reactive | all versions | 2.13.9.Finalio.quarkus.resteasy.reactive:resteasy-reactive:2.13.9.Final |
| ☕Maven | io.quarkus.resteasy.reactive:resteasy-reactive | ≥ 3.0.0.Final&&< 3.2.9.Final | 3.2.9.Finalio.quarkus.resteasy.reactive:resteasy-reactive:3.2.9.Final |
Affected Products
quarkusquarkusDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus.resteasy.reactive:resteasy-reactive, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.quarkus.resteasy.reactive:resteasy-reactive to 2.13.9.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6267 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Quarkus 2.13.9.Final | io.quarkus/quarkus-resteasy:2.13.9.Final-redhat-00003 | RHSA-2024:0494 |
| Red Hat build of Quarkus 3.2.9.Final | io.quarkus/quarkus-resteasy:3.2.9.Final-redhat-00003 | RHSA-2024:0495 |
Frequently Asked Questions
Is CVE-2023-6267 in your dependencies?
Find it across Maven, including transitive dependencies.