The admin backchannel logout route (/k_logout) doesn't verify the signature of the JWT it receives from Keycloak. This causes to the adapter to update the grant manager with a NBF in the future. This effectively logs users out of the app and prevents them from logging in again. Since the tokens received from the code exchange will appear to be in the future, this could be used maliciously against applications using the adapter. Upstream patch: https://github.com/keycloak/keycloak-nodejs-connect/commit/55e54b55d05ba636bc125a8f3d39f0052d13f8f6
This issue has been addressed in the following products: Red Hat Single Sign-On 7.3.2 zip Via RHSA-2019:1456 https://access.redhat.com/errata/RHSA-2019:1456
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2019-10157
This vulnerability is out of security support scope for the following product: * Red Hat Mobile Application Platform Please refer to https://access.redhat.com/support/policy/updates/rhmap for more details