GitHub Advisoryadvisory · Maven

GHSA-xhw6-hjc9-679m Pac4j token validation bypass if OpenID Connect provider supports none algorithm

HIGH Published 2022-01-08 Modified 2023-09-26 Official page ↗
Aliases
CVE-2021-44878
Ecosystem
Maven
Packages
org.pac4j:pac4j-oidc
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Weaknesses
CWE-347
Reviewed
2022-01-07

Affected packages

• Maven org.pac4j:pac4j-oidc: < 4.5.5 → fixed in 4.5.5 • Maven org.pac4j:pac4j-oidc: >= 5.0, < 5.3.1 → fixed in 5.3.1

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.

Related

Alias · CVE (1)

  • CVE-2021-44878 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… vulnerability

Weakness · CWE (1)

  • CWE-347 Improper Verification of Cryptographic Signature weakness

References