Skip to content
Fencer Intel
high 8.6

CVE-2023-6267 json

Quarkus: json payload getting processed prior to security checks when rest resources are used with annotations.

published 2y ago modified 11d ago also EUVD-2024-0298 , GHSA-8j3x-w35r-rw4r

cvss
8.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven io.quarkus.resteasy.reactive:resteasy-reactive 2.13.9.Final, 3.2.9.Final
  • Red Hat Red Hat build of Quarkus 2.13.9.Final 2.13.9.Final-redhat-00003
  • Red Hat Red Hat build of Quarkus 3.2.9.Final 3.2.9.Final-redhat-00003

Is CVE-2023-6267 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-6267 updated cvss 8.6

quarkus: json payload getting processed prior to security checks when rest resources are used with annotations.

  • Red Hat build of OptaPlanner 8 quarkus-resteasy-reactive
    affected: no fix planned “Will not fix”
  • Red Hat Integration Camel K 1 resteasy-core
    affected: no fix available “Fix deferred”
  • Red Hat build of Quarkus 2.13.9.Final quarkus-resteasy 2.13.9.Final-redhat-00003
    fixed: vendor fix RHSA-2024:0494
  • Red Hat build of Quarkus 3.2.9.Final quarkus-resteasy 3.2.9.Final-redhat-00003
    fixed: vendor fix RHSA-2024:0495
  • Red Hat build of Quarkus 2.13.9.Final jna 5.8.0, bson 4.7.2, db2 1.17.3, h2 2.1.214, hppc 0.8.1, jansi 1.18, +986 more Red Hat build of Quarkus 3.2.9.Final jna 5.8.0, lit 2.7.4, bson 4.9.1, db2 1.18.3, h2 2.2.220, jdom 1.1.3, +1045 more Red Hat Fuse 7 resteasy Red Hat Integration Camel Quarkus 2 quarkus-resteasy-reactive
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
GitHub 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven io.quarkus.resteasy.reactive:resteasy-reactive
<2.13.9.Final
>=3.0.0.Final, <3.2.9.Final
2.13.9.Final
3.2.9.Final

Affected products

  • Red Hat Red Hat build of Quarkus 2.13.9.Final
  • Red Hat Red Hat build of Quarkus 3.2.9.Final
  • Red Hat Red Hat build of OptaPlanner 8
  • Red Hat Red Hat Fuse 7
  • Red Hat Red Hat Integration Camel K 1
  • Red Hat Red Hat Integration Camel Quarkus 2

Classification

Weakness
  • CWE-755 Improper Handling of Exceptional Conditions
  • CWE-280 Improper Handling of Insufficient Permissions or Privileges
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.