Skip to content
Fencer Vulns
medium 6.5

CVE-2023-5675 json

Quarkus: authorization flaw in quarkus resteasy reactive and classic when "quarkus.security.jaxrs.deny-unannotated-endpoints" or "quarkus.security.jaxrs.default-roles-allowed" properties are used.

published 2024-04-25 2 y ago modified 2026-11-05 3 d ago also GHSA-25w4-hfqg-4r52 , EUVD-2024-1053

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

Summary

A flaw was found in Quarkus. When a Quarkus RestEasy Classic or Reactive JAX-RS endpoint has its methods declared in the abstract Java class or customized by Quarkus extensions using the annotation processor, the authorization of these methods will not be enforced if it is enabled by either 'quarkus.security.jaxrs.deny-unannotated-endpoints' or 'quarkus.security.jaxrs.default-roles-allowed' properties.

Patch / fix

  • maven io.quarkus:quarkus-resteasy-reactive-common-deployment 3.2.10.Final, 3.6.9, 3.7.1
  • maven io.quarkus:quarkus-resteasy-reactive-common 3.2.10.Final, 3.6.9, 3.7.1
  • 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

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-5675 updated cvss 6.5

quarkus: Authorization flaw in Quarkus RestEasy Reactive and Classic when "quarkus.security.jaxrs.deny-unannotated-endpoints" or "quarkus.security.jaxrs.default-roles-allowed" properties are used.

  • Red Hat A-MQ Clients 2 quarkus-resteasy-reactive Red Hat Cryostat 2 quarkus-resteasy-reactive Red Hat OpenShift Serverless quarkus-resteasy-reactive Red Hat build of Apicurio Registry 2 quarkus-resteasy-reactive Red Hat build of OptaPlanner 8 quarkus-resteasy-reactive Red Hat Fuse 7 quarkus-resteasy-reactive
    +4 more products
    Red Hat Integration Camel K 1 quarkus-resteasy-reactive Red Hat Integration Camel Quarkus 2 quarkus-resteasy-reactive Red Hat JBoss Enterprise Application Platform 8 quarkus-resteasy-reactive Red Hat Process Automation 7 quarkus-resteasy-reactive
    affected: workaround, no fix available “Fix deferred”
  • Red Hat build of Quarkus 2.13.9.Final quarkus-resteasy 2.13.9.Final-redhat-00003, quarkus-resteasy-reactive 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, quarkus-resteasy-reactive 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, +985 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, +1044 more
    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
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven io.quarkus:quarkus-resteasy-reactive-common-deployment
<3.2.10.Final
>=3.3.0, <3.6.9
>=3.7.0, <3.7.1
3.2.10.Final
3.6.9
3.7.1
maven io.quarkus:quarkus-resteasy-reactive-common
<3.2.10.Final
>=3.3.0, <3.6.9
>=3.7.0, <3.7.1
3.2.10.Final
3.6.9
3.7.1

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 A-MQ Clients 2
  • Red Hat Cryostat 2
  • Red Hat OpenShift Serverless
  • Red Hat Red Hat build of Apicurio Registry 2
  • 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
  • Red Hat Red Hat JBoss Enterprise Application Platform 8
  • Red Hat Red Hat Process Automation 7

Classification

Weakness

References

Sources

Fencer Vulns 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.