dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2023-5675

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Quarkus fails to enforce JAX-RS endpoint authorization when methods are declared in abstract Java classes or customized by Quarkus extensions using annotation processors. When 'quarkus.security.jaxrs.deny-unannotated-endpoints' or 'quarkus.security.jaxrs.default-roles-allowed' are enabled, authorization is bypassed for these specific method declarations, allowing unauthenticated or unauthorized access to protected resources.

MitigationUpgrade Quarkus to the patched version when available. In the interim, review all JAX-RS endpoints implemented via abstract classes or extension-customized methods to manually ensure appropriate @RolesAllowed or other security annotations are applied directly on implementing classes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Quarkus version
    Check your project build file (pom.xml or build.gradle) for the Quarkus BOM or dependency version, or run 'quarkus --version' if using the CLI
    Affected if The installed Quarkus version contains this authorization bypass vulnerability (compare to patched version when available)
  2. Verify security JAX-RS configuration
    Inspect your application.properties or application.yaml for 'quarkus.security.jaxrs.deny-unannotated-endpoints' or 'quarkus.security.jaxrs.default-roles-allowed' settings
    Affected if Either property is set to 'true' or has a role value configured, enabling the vulnerable authorization mode
  3. Check for abstract class JAX-RS implementations
    Search your codebase for abstract classes that contain JAX-RS method declarations (methods annotated with @GET, @POST, @PUT, @DELETE, @PATCH, or @OPTIONS)
    Affected if Any abstract class implements JAX-RS endpoints and is used as a base class for concrete JAX-RS resources
  4. Identify extension-customized endpoints
    Review any custom Quarkus extensions or annotation processors that modify JAX-RS endpoint behavior, and check if they generate or modify endpoint methods
    Affected if Custom extensions or annotation processors are used to create or alter JAX-RS method implementations
  5. Confirm implementing classes lack security annotations
    Examine concrete classes that extend abstract JAX-RS base classes, verifying whether @RolesAllowed, @PermitAll, @DenyAll, or other security annotations are applied
    Affected if Implementing classes rely solely on the global security properties without explicit security annotations on their methods

You are affected if your Quarkus version is vulnerable AND either security configuration property is enabled AND your application uses abstract class-based or extension-customized JAX-RS endpoints that lack explicit security annotations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Quarkus to the patched version when available. In the interim, review all JAX-RS endpoints implemented via abstract classes or extension-customized methods to manually ensure appropriate @RolesAllowed or other security annotations are applied directly on implementing classes.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5675 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-5675 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data