
Cloud Vulnerability DB
A community-led vulnerabilities database
The ACS endpoint (saml-sp/login) didn't check two parts of a SAML login Response, and followed an unvalidated redirect after login.
1. AudienceRestriction was not validated. An assertion the IdP issued for a different service provider
could log its subject into Craft, as long as it also passed the Recipient and Destination checks. That's possible when:
SubjectConfirmationData/@Recipient (the Recipient check passes when it's absent), orRelayState, a plain form field outside the signature. On SP-initiated logins it comes from the login link's
RelayState parameter and is echoed back by the IdP. A link such as
https://site.example/actions/saml-sp/login/request?RelayState=https://evil.example therefore sends the user
through a genuine login to an attacker's page, for example a fake "session expired, re-enter your password" form.
Protocol-relative (//evil.example), userinfo (https://site.example@evil.example) and lookalike hosts were also
followed.
Versions 4.3.3 and 5.2.8:
AudienceRestriction containing this SP's Entity ID, and rejects assertions that don't have one;SubjectConfirmationData, whose InResponseTo isn't an AuthnRequest this site
issued in the last hour. Each request ID is single-use and is bound to the issuing browser session when that
session's cookie is present;RelayState only to a path or an http(s) URL on the request host, a Craft site host, or a host listed
in the new allowedRedirectHosts setting; any other target goes to Craft's default post-login URL.
IdP-initiated (unsolicited) logins are still accepted by default. Set allowIdpInitiatedLogin to false inconfig/saml-sp.php to reject them.
After upgrading, if logins fail with "not a valid audience" or "no AudienceRestriction", set the IdP's audience
to this site's Entity ID.
None in configuration. To reduce exposure until you can upgrade:
Recipient;requireResponseToBeSigned, requireAssertionToBeSigned);EVENT_BEFORE_RELAYSTATE_REDIRECT to replace $event->redirect with a same-site URL.While allowIdpInitiatedLogin is true, an unsolicited assertion can still be replayed within its validity
window. Preventing that needs a used-assertion-ID cache, planned separately.
Patched in 4.3.3 (Craft 4) and 5.2.8 (Craft 5). Versions before 4.0 (Craft 3) are no longer maintained and won't be patched; upgrade to 4.3.3 or later.
The regression tests added with the fix (tests/unit/controllers/LoginControllerTest.php) post IdP-signed
Responses to LoginController::actionIndex. On unpatched versions each of these logs the user in (or, for the last one, redirects off-site); on 5.2.8 each is rejected:
testAssertionForAnotherAudienceIsRejectedtestAssertionWithoutAudienceRestrictionIsRejectedtestResponseToAnUnknownRequestIsRejectedtestSubjectConfirmationInResponseToAnUnknownRequestIsRejectedtestResponseToOurAuthnRequestCannotBeReplayedtestOffSiteRelayStateIsNotFollowed (absolute, protocol-relative, userinfo, lookalike and javascript: targets)Source: NVD
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."