Homepage

org.keycloak:keycloak-quarkus-server@21.1.2 vulnerabilities

  • latest version

    26.2.0

  • first published

    4 years ago

  • latest version published

    8 days ago

  • licenses detected

  • package registry

    View on Maven Central Repository
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the org.keycloak:keycloak-quarkus-server package. This does not include vulnerabilities belonging to this package’s dependencies.

    How to fix?

    Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    Allocation of Resources Without Limits or Throttling

    Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to the improper handling of HTTP metrics. An attacker can cause a denial of service by sending crafted requests that lead to metrics explosion.

    How to fix Allocation of Resources Without Limits or Throttling?

    There is no fixed version for org.keycloak:keycloak-quarkus-server.

    [0,)
    • H
    Use of Hard-coded Credentials

    Affected versions of this package are vulnerable to Use of Hard-coded Credentials due to sensitive runtime values being captured during the build process and embedded as default values in bytecode.

    Note:

    For versions 26.x, sensitive data specified directly in environment variables during the build process is also stored as a default value, making it accessible during runtime. Indirect usage of environment variables for SPI options and Quarkus properties is also vulnerable due to unconditional expansion by PropertyMapper logic, capturing sensitive data as default values.

    How to fix Use of Hard-coded Credentials?

    Upgrade org.keycloak:keycloak-quarkus-server to version 26.0.6 or higher.

    [,26.0.6)
    • M
    HTTP Request Smuggling

    Affected versions of this package are vulnerable to HTTP Request Smuggling due to improper handling of proxy headers resulting in costly DNS resolution operations. An attacker could tie up IO threads and potentially cause a denial of service by exploiting these operations.

    Notes:

    1. This is only exploitable if the attacker has access to send requests to a Keycloak instance that is configured to accept proxy headers, specifically when reverse proxies do not overwrite incoming headers, and Keycloak is configured to trust these headers.

    2. For versions 26.x, this is only exploitable if the realm must have SslRequired=EXTERNAL (the default), HTTP must be enabled, the instance must not be using a full hostname URL, access must come from behind a proxy (assuming the proxy overwrites the X-Forwarded-For header), and trusted proxies must not be set or must incorrectly trust the client from which the request is originating.

    How to fix HTTP Request Smuggling?

    Upgrade org.keycloak:keycloak-quarkus-server to version 26.0.6 or higher.

    [,26.0.6)
    Go back to all versions of this package