org.keycloak:keycloak-quarkus-server 22.0.5 vulnerabilities

Direct Vulnerabilities

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

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
M Uncontrolled Search Path Element Affected versions of this package are vulnerable to Uncontrolled Search Path Element via the `/admin` application path relative to `/realms` when accessed through a proxy that does not properly restrict or normalize URLs. An attacker can gain unauthorized access to sensitive administrative functions by crafting requests with relative or non-normalized paths. The responsibility for validating paths is generally delegated to the proxy, but the project maintainers have determined that the default behavior of not accepting non-normalized paths should be enforced by the library, for defense in depth. How to fix Uncontrolled Search Path Element? Upgrade `org.keycloak:keycloak-quarkus-server` to version 26.4.0 or higher.	[,26.4.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: 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. 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)

Vulnerability

Vulnerable Version

Uncontrolled Search Path Element

Affected versions of this package are vulnerable to Uncontrolled Search Path Element via the /admin application path relative to /realms when accessed through a proxy that does not properly restrict or normalize URLs. An attacker can gain unauthorized access to sensitive administrative functions by crafting requests with relative or non-normalized paths.

The responsibility for validating paths is generally delegated to the proxy, but the project maintainers have determined that the default behavior of not accepting non-normalized paths should be enforced by the library, for defense in depth.

How to fix Uncontrolled Search Path Element?

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

[,26.4.0)

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)

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:

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.
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)

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

latest version

latest non vulnerable version

first published

latest version published

licenses detected

package registry

Direct Vulnerabilities

Fix vulnerabilities automatically