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.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.5epss 0.5%
exploitation probability
0.5%top 61% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Affected products
quarkus-resteasy-reactiveRed Hat · A-MQ Clients 2Red Hat · Cryostat 2Red Hat · OpenShift ServerlessRed Hat · Red Hat build of Apicurio Registry 2Red Hat · Red Hat build of OptaPlanner 8Red Hat · Red Hat build of Quarkus 2.13.9.FinalRed Hat · Red Hat build of Quarkus 3.2.9.FinalRed Hat · Red Hat Fuse 7Red Hat · Red Hat Integration Camel K 1Red Hat · Red Hat Integration Camel Quarkus 2Red Hat · Red Hat JBoss Enterprise Application Platform 8Red Hat · Red Hat Process Automation 7