Description
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.
Remediation
References
https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae
https://openid.net/specs/openid-connect-core-1_0.html#IDToken
https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html
Related Vulnerabilities
CVE-2023-46652 Vulnerability in maven package org.jenkins-ci.plugins:lambdatest-automation
CVE-2021-21166 Vulnerability in npm package electron
CVE-2022-21721 Vulnerability in npm package next
CVE-2023-24998 Vulnerability in maven package org.apache.tomcat:tomcat-catalina
CVE-2020-5219 Vulnerability in npm package angular-expressions