pac4j-oidc before 6.5.6 Authentication Bypass via Access Token Substitution
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.9epss 0.1%
exploitation probability
0.1%top 97% of all CVEs
observed exploitation
nono source reports it
pac4j-oidc before 6.5.6 accepts OIDC callbacks carrying only an access token without authorization code or ID token validation. Attackers can substitute access tokens minted for other clients to create authenticated sessions without proper issuer, audience, nonce, or subject verification.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Affected products
pac4j · pac4jReferences
https://github.com/pac4j/pac4jhttps://github.com/pac4j/pac4j/blob/pac4j-parent-6.5.5/pac4j-oidc/src/main/java/org/pac4j/oidc/credentials/extractor/OidcCredentialsExtractor.javahttps://github.com/pac4j/pac4j/commit/2270c3ff70e93cc43831e75702acd5135531237ehttps://www.pac4j.org/blog/security-advisory-pac4j-core-oidc-saml.htmlhttps://www.vulncheck.com/advisories/pac4j-oidc-before-6.5.6-authentication-bypass-via-access-token-substitution