Skip to content

Keycloak configured with empty client secret

Critical
tobybellwood published GHSA-jr7f-g7p4-v985 Apr 11, 2022

Package

keycloak (lagoon-core)

Affected versions

2.5.0

Patched versions

2.6.0

Description

Impact

A new keycloak service-api client was added in 2.5.0 in order to facilitate a new ssh portal in a future release. This client is configured with the "token exchange" permission which allows it to generate access tokens for users. A mismatched deployment between lagoon-core and lagoon-charts caused the client to be created with an empty secret.

An attacker with advanced knowledge of the Keycloak and Lagoon ecosystems would be able to craft an exploit that allows them to obtain an access token for any user in the lagoon realm, including admin/platform-owner users. They would then be able to access all fields/mutations on the Lagoon GraphQL api.

We're not aware of any methods by which an attacker could 1) gain admin access to the keycloak master realm or 2) access the lagoon realm settings via the keycloak UI/API.

Patches

This issue has been addressed in 2.6.0, and further improvements will follow in a subsequent release.

Workarounds

The immediate mitigation is to log in to Keycloak, go to the service-api client, and click Regenerate secret.

For more information

If you have any questions or comments about this advisory:

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H

CVE ID

No known CVE

Weaknesses

No CWEs

Credits