Prowler is a cloud security platform. Prior to 5.30.3, Prowler's SAML authentication flow trusted the email domain asserted in a SAMLResponse when deciding which tenant should receive the final token, and the ACS finish logic in api/src/backend/api/v1/views.py recalculated the tenant from user.email instead of binding token issuance to the validated SAML configuration. An authenticated attacker with a controlled SAML IdP could complete a valid SAML flow for an attacker-controlled domain while asserting an email address from another configured domain, causing a SAMLToken and tenant-scoped JWT to be issued for the wrong tenant and enabling cross-tenant account takeover.
This issue is fixed in version 5.30.3.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
References 5
https://github.com/prowler-cloud/prowler/commit/bf3b5c2ba713e533014927141b64948…
security-advisories@github.com
https://github.com/prowler-cloud/prowler/commit/f5ff30ad175bd2edf02cd28872653c1…
security-advisories@github.com
https://github.com/prowler-cloud/prowler/pull/11650
security-advisories@github.com
https://github.com/prowler-cloud/prowler/releases/tag/5.30.3
security-advisories@github.com
https://github.com/prowler-cloud/prowler/security/advisories/GHSA-h8m9-jgf8-vwvp
security-advisories@github.com