Encrypted ID token or JARM response accepted without a nested signature in erlef oidcc
erlef oidcc
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| erlef oidcc |
| No fix yet |
| erlef oidcc |
| No fix yet |
Original description
Improper Verification of Cryptographic Signature vulnerability in erlef oidcc allows an unauthenticated attacker to impersonate an arbitrary user via an encrypted ID token or JARM response carrying no nested signature. OpenID Connect Core 1.0 section 2 requires that an encrypted ID token be signed then encrypted, with the result being a Nested JWT, and JARM processing rule 5 requires the client to check the signature unconditionally. oidcc instead accepted a JWE wrapping unsigned claims as fully validated, so anyone holding the relying party's public encryption key could mint a token with an arbitrary sub, iss, and aud without possessing the provider's signing key.