UAA accepts SAML Encrypted Assertions authentication bypass
Cloud Foundry UAA · Cloud Foundry CF Deployment
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Cloud Foundry UAA |
| No fix yet |
| Cloud Foundry CF Deployment |
| No fix yet |
Original description
Cloud Foundry UAA incorrectly treated XML encryption to the Service Provider (confidentiality) as a substitute for XML signatures from the Identity Provider (authenticity) in two SAML flows: the OAuth 2.0 SAML2 bearer grant (token endpoint) and browser SSO (ACS) when wantAssertionSigned is set to false. Assertions or responses that were unsigned but contained encrypted content could still be accepted. Encryption uses the SP's public key from published metadata, therefore, any party, not only a trusted IdP, can produce ciphertext UAA can decrypt; successful decryption therefore does not prove the IdP issued the message.