Skip to content

Quarkus: authorization flaw in quarkus resteasy reactive and classic

Moderate severity GitHub Reviewed Published Apr 25, 2024 to the GitHub Advisory Database • Updated Jun 11, 2024

Package

maven io.quarkus:quarkus-resteasy-reactive-common (Maven)

Affected versions

< 3.2.10.Final
>= 3.3.0, < 3.6.9
>= 3.7.0, < 3.7.1

Patched versions

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

Description

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.

References

Published by the National Vulnerability Database Apr 25, 2024
Published to the GitHub Advisory Database Apr 25, 2024
Reviewed Apr 25, 2024
Last updated Jun 11, 2024

Severity

Moderate
6.5
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Weaknesses

CVE ID

CVE-2023-5675

GHSA ID

GHSA-25w4-hfqg-4r52

Source code

Credits

Checking history
See something to contribute? Suggest improvements for this vulnerability.