Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Pac4J | Pac4J | < 4.5.5 |
Related Weaknesses (CWE)
References
- https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281aePatchThird Party Advisory
- https://openid.net/specs/openid-connect-core-1_0.html#IDTokenProductThird Party Advisory
- https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.htmlMitigationVendor Advisory
- https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281aePatchThird Party Advisory
- https://openid.net/specs/openid-connect-core-1_0.html#IDTokenProductThird Party Advisory
- https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.htmlMitigationVendor Advisory
FAQ
What is CVE-2021-44878?
CVE-2021-44878 is a vulnerability with a CVSS score of 7.5 (HIGH). 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 "idto...
How severe is CVE-2021-44878?
CVE-2021-44878 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2021-44878?
Check the references section above for vendor advisories and patch information. Affected products include: Pac4J Pac4J.