REDHAT-BUG-2031904
First published: Mon Dec 13 2021(Updated: )
This issue is the result of code found in the exception here: <a href="https://github.com/keycloak/keycloak/blob/48835576daa158443f69917ac309e1a7c951bc87/services/src/main/java/org/keycloak/authentication/AuthenticationProcessor.java#L1045">https://github.com/keycloak/keycloak/blob/48835576daa158443f69917ac309e1a7c951bc87/services/src/main/java/org/keycloak/authentication/AuthenticationProcessor.java#L1045</a> Reproduction: 1. Sign in as Admin user in first tab. 2. In that tab create new user in keycloak admin section > intercept user creation request and modify it by including malicious js script there (in username field). 3. Sign in as newly created user in second tab (same browser window but second tab). 4. Navigate back to first tab where you are signed in as admin, navigate to admin console which lists all application users. 5. Choose any user (except newly created malicious one) – modify anything for that user in his settings. E.g. navigate to credentials tab and set new credentials for him. Also set new password as temporary. 6. After update for that user is made, use impersonate option on that modified user. 7. You should see window with form which requires providing new credentials – fill it and submit request. 8. Just after submiting request user will get notified that “You are already authenticated as different user ‘[user + payload]’ in this session. Please sign out first.” And malicious payload will be executed instantly.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Keycloak |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/keycloak/keycloak/blob/48835576daa158443f69917ac309e1a7c951bc87/services/src/main/java/org/keycloak/authentication/AuthenticationProcessor.java#L1045
- https://access.redhat.com/errata/RHSA-2023:1043
- https://access.redhat.com/errata/RHSA-2023:1044
- https://access.redhat.com/errata/RHSA-2023:1045
- https://access.redhat.com/errata/RHSA-2023:1047
- https://access.redhat.com/errata/RHSA-2023:1049
- https://access.redhat.com/security/cve/cve-2022-1438
- https://bugzilla.redhat.com/show_bug.cgi?id=2031904
Frequently Asked Questions
What is the severity of REDHAT-BUG-2031904?
The severity of REDHAT-BUG-2031904 is classified as high due to potential security implications.
How do I fix REDHAT-BUG-2031904?
To fix REDHAT-BUG-2031904, update to the latest version of Red Hat Build of Keycloak.
What are the potential impacts of REDHAT-BUG-2031904?
The potential impacts of REDHAT-BUG-2031904 include unauthorized access and possible data breaches.
Which versions of Keycloak are affected by REDHAT-BUG-2031904?
All versions of Red Hat Build of Keycloak prior to the patch release are impacted by REDHAT-BUG-2031904.
Where can I find more information about REDHAT-BUG-2031904?
For more information about REDHAT-BUG-2031904, check the official Red Hat bug report and documentation.
- agent/references
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2022-1438
- agent/severity
- agent/description
- agent/event
- agent/source
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/red hat
- canonical/keycloak