CVEvulnerability
CVE-2021-44878
7.5 HIGH
Official page ↗
- Status
- Modified
- Published
- 2022-01-06
- Last modified
- 2026-06-17
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 7.5 HIGH — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- CVSS 2.0 ([email protected])
- 5.0 MEDIUM — AV:N/AC:L/Au:N/C:N/I:P/A:N
- Weaknesses
- CWE-347
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.
Affected configurations
• pac4j pac4j (< 4.5.5)
• pac4j pac4j (>= 5.0.0 < 5.3.1)
Related
Weakness · CWE (1)
- CWE-347 Improper Verification of Cryptographic Signature weakness
References
- https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae Patch, Third Party Advisory
- https://openid.net/specs/openid-connect-core-1_0.html#IDToken Product, Third Party Advisory
- https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html Mitigation, Vendor Advisory
- https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae Patch, Third Party Advisory
- https://openid.net/specs/openid-connect-core-1_0.html#IDToken Product, Third Party Advisory
- https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html Mitigation, Vendor Advisory