First published: Tue Apr 25 2017(Updated: )
It was found that the Keycloak Node.js adapter 2.5 - 3.0 did not handle invalid tokens correctly. An attacker could use this flaw to bypass authentication and gain access to restricted information, or to possibly conduct further attacks.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/keycloak | <3.1.0 | 3.1.0 |
Keycloak Keycloak-nodejs-auth-utils | =2.5.0 | |
Keycloak Keycloak-nodejs-auth-utils | =2.5.0-cr1 | |
Keycloak Keycloak-nodejs-auth-utils | =2.5.1 | |
Keycloak Keycloak-nodejs-auth-utils | =2.5.2 | |
Keycloak Keycloak-nodejs-auth-utils | =2.5.3 | |
Keycloak Keycloak-nodejs-auth-utils | =2.5.4 | |
Keycloak Keycloak-nodejs-auth-utils | =2.5.5 | |
Keycloak Keycloak-nodejs-auth-utils | =2.5.6 | |
Keycloak Keycloak-nodejs-auth-utils | =2.5.7 | |
Keycloak Keycloak-nodejs-auth-utils | =3.0.0 | |
Keycloak Keycloak-nodejs-auth-utils | =3.0.0-cr1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.