Am I affected?
Description
The Ueberauth.Strategy.Apple.Token.payload/2 function verifies the JWT signature of the callback id_token against Apple's JWKS but does not validate any registered claims. The iss, aud, exp, and iat claims are read from the token and passed on to Ueberauth.Strategy.Apple.handle_callback!/1, which derives the logged-in user's uid and email directly from the unvalidated sub claim.
An attacker who obtains any Apple-signed ID token bearing the victim's sub (via a captured expired token, or via an ID token issued to a sibling client in the same Apple developer team) can replay it against the vulnerable callback and be authenticated as the victim. The absent exp check makes stolen tokens usable indefinitely, and the absent aud check enables cross-application account takeover across clients that share an Apple developer team.
This issue affects ueberauth_apple: from 0.1.0 before 0.6.2.
Weaknesses & attack patterns
Weakness
CWE-290
·
Authentication Bypass by Spoofing
in catalog →
MITRE ↗
Attack patterns
CAPEC-60
·
Reusing Session IDs (aka Session Replay)
MITRE ↗
Affected — Hex / ueberauth_apple Hex.pm ↗ Repository ↗
modules · source files · routines
Affected — GitHub / ueberauth/ueberauth_apple Repository ↗
modules · source files · routines
References
Credits
CVSS breakdown
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N