CVE-2023-5675VulnerabilityPublished 25 Apr 2024Updated 20 Nov 2025

CVE-2023-5675: quarkus-resteasy · Improper Authorization

Affects quarkus-resteasySource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenio.quarkus/quarkus-resteasy`pkg:maven/io.quarkus/quarkus-resteasy`Other threats	Affected =3.2.0 =3.6.0 =3.7.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2023-5675, European organizations should: 1) Upgrade Quarkus to a patched version as soon as it becomes available from the vendor or community, ensuring the fix addresses authorization enforcement on abstract or annotated methods. 2) Review and audit all REST endpoints, especially those declared in abstract classes or customized via annotation processors, to verify that authorization annotations are correctly applied and enforced. 3) Temporarily disable or avoid using the 'quarkus.security.jaxrs.deny-unannotated-endpoints' and 'quarkus.security.jaxrs.default-roles-allowed' properties if they cannot be reliably enforced, or implement additional manual authorization checks in code. 4) Employ runtime application self-protection (RASP) or API gateways with strict access control policies to add defense-in-depth. 5) Conduct penetration testing focused on authorization bypass scenarios to detect potential exploitation. 6) Monitor application logs and network traffic for unusual access patterns to REST endpoints. 7) Educate developers about secure use of abstract classes and annotation processors in Quarkus to prevent similar issues. These steps go beyond generic patching by emphasizing configuration review, code auditing, and layered security controls.

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.

Impact

The primary impact of CVE-2023-5675 is unauthorized access to REST endpoints that should be protected by role-based authorization policies. For European organizations, this could lead to unauthorized disclosure of sensitive information, unauthorized modification of data, or execution of privileged operations within applications built on vulnerable Quarkus versions. Industries such as finance, healthcare, government, and critical infrastructure that rely on Java microservices for business-critical operations are at heightened risk. The vulnerability undermines the confidentiality and integrity of application data and services, potentially leading to regulatory non-compliance (e.g., GDPR violations) if personal or sensitive data is exposed. Since exploitation requires no authentication or user interaction and can be performed remotely, attackers can leverage this flaw to gain unauthorized access at scale. This could facilitate further lateral movement or escalation within affected networks. The lack of known exploits in the wild currently reduces immediate risk, but the medium severity score and ease of exploitation warrant proactive mitigation. European organizations with public-facing APIs or internal services using Quarkus should consider this a significant security concern.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Nov 2025, 18:45 UTC

Technical details

References

Community reviews

Related threats