Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

redhat логотип

CVE-2023-6236

Опубликовано: 02 апр. 2024
Источник: redhat
CVSS3: 7.3

Описание

A flaw was found in Red Hat Enterprise Application Platform 8. 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. EAP-7 does not provide the vulnerable provider-url configuration option in its OIDC implementation and is not affected by this flaw.

Затронутые пакеты

ПлатформаПакетСостояниеРекомендацияРелиз
Red Hat JBoss Enterprise Application Platform 7eapNot affected
Red Hat JBoss Enterprise Application Platform Expansion PackwildflyUnder investigation
Red Hat JBoss Enterprise Application Platform 8eapFixedRHSA-2024:358304.06.2024
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8eap8-elytron-webFixedRHSA-2024:358004.06.2024
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8eap8-wildfly-elytronFixedRHSA-2024:358004.06.2024
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 9eap8-elytron-webFixedRHSA-2024:358104.06.2024
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 9eap8-wildfly-elytronFixedRHSA-2024:358104.06.2024

Показывать по

Дополнительная информация

Статус:

Moderate
Дефект:
CWE-345
https://bugzilla.redhat.com/show_bug.cgi?id=2250812EAP: OIDC app attempting to access the second tenant, the user should be prompted to log

7.3 High

CVSS3

Связанные уязвимости

CVSS3: 7.3
nvd
почти 2 года назад

A flaw was found in Red Hat Enterprise Application Platform 8. 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. EAP-7 does not provide the vulnerable provider-url configuration option in its OIDC implementation and is not affected by this flaw.

CVSS3: 7.3
github
почти 2 года назад

WildFly Elytron: OIDC app attempting to access the second tenant, the user should be prompted to log

7.3 High

CVSS3