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.
Security readout for executives and security teams
Plain-English summary
Prowler versions before 5.30.3 could issue access tokens to the wrong tenant during SAML login. A logged-in attacker controlling their own SAML identity provider could claim an email domain belonging to another tenant and receive that tenant's token. This creates cross-tenant account takeover risk.
Executive priority
Treat this as urgent for any Prowler environment using SAML. The issue can cross tenant boundaries and compromise confidentiality and integrity, but the supplied evidence does not show active exploitation.
Technical view
The SAML ACS finish path recalculated tenant selection from user.email in the SAMLResponse instead of binding token issuance to the validated SAML configuration. This authentication flaw is CWE-287 with CVSS 9.6, network exploitable, low complexity, low privileges, no user interaction, changed scope, and high confidentiality and integrity impact.
Likely exposure
Prowler deployments running versions before 5.30.3 are affected, especially where SAML SSO and tenant/domain mapping are configured. The provided sources do not clarify separate exposure differences between SaaS, self-hosted, or specific deployment modes.
Exploitation context
The bundle says exploitation requires an authenticated attacker with a controlled SAML IdP and a target domain already configured in Prowler. KEV is false, and no provided source states active exploitation in the wild.
Researcher notes
Focus review on SAML ACS tenant resolution and token issuance. The vulnerable behavior is trusting email-domain claims in the SAMLResponse rather than the validated SAML configuration. Do not assume exploitability beyond Prowler before 5.30.3 from these sources.
Mitigation direction
Upgrade Prowler to version 5.30.3 or later.
Review the GitHub security advisory and 5.30.3 release notes.
If upgrade is delayed, check vendor guidance for supported temporary controls.
Review SAML tenant/domain configuration for unexpected or stale entries.
Validation and detection
Inventory Prowler versions and flag anything below 5.30.3.
Identify deployments with SAML authentication enabled.
Confirm tenant token issuance is tied to validated SAML configuration after upgrade.
Review authentication logs for unusual SAML logins across tenant domains.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-287 · source CWE mapping
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.