Impact
When a response is processed, the issuer of the Identity Provider is not sufficiently validated. This could allow a malicious identity provider to craft a Saml2 response that is processed as if issued by another identity provider. It is also possible for a malicious end user to cause stored state intended for one identity provider to be used when processing the response from another provider.
An application is impacted if they rely on any of these features in their authentication/authorization logic:
- the issuer of the generated identity and claims
- items in the stored request state (AuthenticationProperties)
Patches
Patched in version 2.9.2 and 1.0.3. All previous versions are vulnerable.
Workarounds
The AcsCommandResultCreated notification can be used to add the validation required if an upgrade to patched packages is not possible.
References
The patch is linked to Sustainsys/Saml2#712 and Sustainsys/Saml2#713
References
c53robin Finder
Impact
When a response is processed, the issuer of the Identity Provider is not sufficiently validated. This could allow a malicious identity provider to craft a Saml2 response that is processed as if issued by another identity provider. It is also possible for a malicious end user to cause stored state intended for one identity provider to be used when processing the response from another provider.
An application is impacted if they rely on any of these features in their authentication/authorization logic:
Patches
Patched in version 2.9.2 and 1.0.3. All previous versions are vulnerable.
Workarounds
The
AcsCommandResultCreatednotification can be used to add the validation required if an upgrade to patched packages is not possible.References
The patch is linked to Sustainsys/Saml2#712 and Sustainsys/Saml2#713
References