Authentication bypass via accepted unsigned ID tokens
Published Jan 6, 2022 · Updated Aug 4, 2024
Authentication bypass in pac4j-oidc before 4.5.5 and 5.0 through 5.3.0 allows remote attackers to forge accepted ID tokens. TokenValidator builds an IDTokenValidator for the provider-advertised none algorithm without requiring allowUnsignedIdTokens, so an empty signature passes validation. Exploitation requires an OIDC provider that advertises none; the accepted forged token lets an unauthenticated attacker impersonate an authenticated identity.
Summary
What happened
Authentication bypass in pac4j-oidc before 4.5.5 and 5.0 through 5.3.0 allows remote attackers to forge accepted ID tokens. TokenValidator builds an IDTokenValidator for the provider-advertised none algorithm without requiring allowUnsignedIdTokens, so an empty signature passes validation. Exploitation requires an OIDC provider that advertises none; the accepted forged token lets an unauthenticated attacker impersonate an authenticated identity.
The record
- CVE
- CVE-2021-44878
- Published
- Jan 6, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 6, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo