GHSA-25w4-hfqg-4r52 Quarkus: authorization flaw in quarkus resteasy reactive and classic

• Maven io.quarkus:quarkus-resteasy-reactive-common-deployment: < 3.2.10.Final → fixed in 3.2.10.Final • Maven io.quarkus:quarkus-resteasy-reactive-common: < 3.2.10.Final → fixed in 3.2.10.Final • Maven io.quarkus:quarkus-resteasy-reactive-common-deployment: >= 3.3.0, < 3.6.9 → fixed in 3.6.9 • Maven io.quarkus:quarkus-resteasy-reactive-common: >= 3.3.0, < 3.6.9 → fixed in 3.6.9 • Maven io.quarkus:quarkus-resteasy-reactive-common-deployment: >= 3.7.0, < 3.7.1 → fixed in 3.7.1 • Maven io.quarkus:quarkus-resteasy-reactive-common: >= 3.7.0, < 3.7.1 → fixed in 3.7.1

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. While backports of this fix exist in versions 3.6.9 and 3.7.1 users of older versions are encouraged to update to the 3.8.x LTS branch.