A flaw was found in all versions of Keycloak before 10.0.0, where the NodeJS adapter did not support the verify-token-audience. This flaw results in some users having access to sensitive information outside of their permissions.
The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Keycloak | Redhat | * | 10.0.0 (excluding) |
Red Hat Single Sign-On 7.4.1 | RedHat | * |