Headline
GHSA-jpmx-996v-48fm: WildFly Elytron: OIDC app attempting to access the second tenant, the user should be prompted to log
A flaw was found in JBoss EAP. When an OIDC app that serves multiple tenants attempts to access the second tenant, it should prompt the user to log in again since the second tenant is secured with a different OIDC configuration. The underlying issue is in OidcSessionTokenStore when determining if a cached token should be used or not. This logic needs to be updated to take into account the new “provider-url” option in addition to the “realm” option.
Skip to content
Actions
Automate any workflow
Packages
Host and manage packages
Security
Find and fix vulnerabilities
Codespaces
Instant dev environments
Copilot
Write better code with AI
Code review
Manage code changes
Issues
Plan and track work
Discussions
Collaborate outside of code
GitHub Sponsors
Fund open source developers
* The ReadME Project
GitHub community articles
- Pricing
Provide feedback
Saved searches****Use saved searches to filter your results more quickly
Sign up
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2023-6236
WildFly Elytron: OIDC app attempting to access the second tenant, the user should be prompted to log
High severity GitHub Reviewed Published Apr 10, 2024 to the GitHub Advisory Database • Updated Apr 10, 2024
Package
maven org.wildfly.security:wildfly-elytron-http-oidc (Maven)
Affected versions
<= 2.2.2
Description
Published to the GitHub Advisory Database
Apr 10, 2024
Last updated
Apr 10, 2024