CVE-2023-6236

{"id": "CVE-2023-6236", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "secalert@redhat.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.3, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 3.4, "exploitabilityScore": 3.9}]}, "published": "2024-04-10T01:15:17.383", "references": [{"url": "https://access.redhat.com/errata/RHSA-2024:3580", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:3581", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:3583", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/security/cve/CVE-2023-6236", "source": "secalert@redhat.com"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2250812", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:3580", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:3581", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:3583", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/security/cve/CVE-2023-6236", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2250812", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "secalert@redhat.com", "description": [{"lang": "en", "value": "CWE-345"}]}], "descriptions": [{"lang": "en", "value": "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.\r\n\r\nEAP-7 does not provide the vulnerable provider-url configuration option in its OIDC implementation and is not affected by this flaw."}, {"lang": "es", "value": "Se encontr\u00f3 una falla en JBoss EAP. Cuando una aplicaci\u00f3n OIDC que atiende a varios inquilinos intenta acceder al segundo inquilino, deber\u00eda solicitarle al usuario que inicie sesi\u00f3n nuevamente, ya que el segundo inquilino est\u00e1 protegido con una configuraci\u00f3n OIDC diferente. El problema subyacente est\u00e1 en OidcSessionTokenStore al determinar si se debe utilizar o no un token almacenado en cach\u00e9. Esta l\u00f3gica debe actualizarse para tener en cuenta la nueva opci\u00f3n \"proveedor-url\" adem\u00e1s de la opci\u00f3n \"realm\"."}], "lastModified": "2024-11-21T08:43:25.840", "sourceIdentifier": "secalert@redhat.com"}