Skip to content

← Public intelligence

Maven package

io.quarkus.resteasy.reactive:resteasy-reactive

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.3MavenPublished

    Quarkus: security checks in resteasy reactive may trigger a denial of service

    CVE-2024-1726 · GHSA-mv64-86g8-cqq7

    Affected
    • Maven io.quarkus.resteasy.reactive:resteasy-reactive >= 3.8.0.CR1, <= 3.8.0.CR1; >= 3.3.0.CR1, < 3.7.4; < 3.2.11.Final
    Fixed in
    3.8.03.2.11.Final3.7.4· Vendor fix available
    Issue
    A flaw was discovered in the RESTEasy Reactive implementation in Quarkus. Due to security checks for some JAX-RS endpoints being performed after serialization, more processing resources are consumed while the HTTP request is checked. In certain configurations, if an attacker has knowledge of any POST, PUT, or PATCH request paths, they can potentially identify vulnerable endpoints and trigger excessive resource usage as the endpoints process the requests. This can result in a denial of service.

    Recommended action: Upgrade to 3.8.0, 3.7.4 or 3.2.11.Final by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 8.8MavenPublished

    Quarkus Improper Handling of Insufficient Permissions or Privileges and Improper Handling of Exceptional Conditions vulnerability

    CVE-2023-6267 · GHSA-8j3x-w35r-rw4r

    Affected
    • Maven io.quarkus.resteasy.reactive:resteasy-reactive < 2.13.9.Final; >= 3.0.0.Final, < 3.2.9.Final
    Fixed in
    2.13.9.Final3.2.9.Final· Vendor fix available
    Issue
    A flaw was found in the json payload. If annotation based security is used to secure a REST resource, the JSON body that the resource may consume is being processed (deserialized) prior to the security constraints being evaluated and applied. This does not happen with configuration based security.

    Recommended action: Upgrade to 3.2.9.Final or 2.13.9.Final by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →