CVE Vulnerability

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 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.

5 /10

CVSS v2.0 :

V3 Legend

Vector :

Exploitability : 10 / Impact : 2.9

Attack Vector

Attack Complexity

Privileges Required

User Interaction

Confidentiality Impact NONE

Integrity Impact PARTIAL

Availability Impact NONE

Scope

7.5 /10

CVSS v3.0 : HIGH

V3 Legend

Vector :

Exploitability : 3.9 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact HIGH

Availability Impact NONE

Scope UNCHANGED

References
Link Resource
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
Configurations

Configuration 1

cpe:2.3:a:pac4j:pac4j:*:*:*:*:*:*:*:*
cpe:2.3:a:pac4j:pac4j:*:*:*:*:*:*:*:*
Information

Published : 2022-01-06 01:15

Updated : 2022-05-13 03:51

NVD link : CVE-2021-44878

Mitre link : CVE-2021-44878

Products Affected
No products.
CWE
CWE-347

Improper Verification of Cryptographic Signature