If an OpenID Connect provider supports the "none" algorithm (i.e., tokens with no signature), pac4j v5.3.0 (and prior) does not refuse it without an explicit configuration on its side or for the "idtoken" response type which is not secure and violates the OpenID Core Specification. The "none" algorithm does not require any signature verification when validating the ID tokens, which allows the attacker to bypass the token validation by injecting a malformed ID token using "none" as the value of "alg" key in the header with an empty signature value.
oryginał ENCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NPac4j
APPPac4J< 4.5.55.0.0 – 5.3.1 (bez)
Powiązane podatności
PAC4J is vulnerable to Cross-Site Request Forgery (CSRF). A malicious attacker can craft a specially designed ...
PAC4J is vulnerable to LDAP Injection in multiple methods. A low-privileged remote attacker can inject crafted...
The SAML identifier generated within SAML2Utils.java was found to make use of the apache commons-lang3 RandomS...