Iangcarroll

**Name of the Vulnerable Software and Affected Versions** Fleet versions prior to 4.9.1 **Description** The issue exposes a limited ability to spoof SAML authentication with missing audience verification, impacting deployments using SAML SSO in two specific cases. A malicious or compromised Service Provider (SP) could reuse the SAML response to log into Fleet as a user, if the user has an account with the same email in Fleet and signs into the malicious SP via SAML SSO from the same Identity Provider (IdP) configured with Fleet. Additionally, a user with an account in Fleet could reuse a SAML response intended for another SP to log into Fleet, if the user is blocked from Fleet in the IdP but continues to have an account in Fleet. **Recommendations** For versions prior to 4.9.1: Reduce the length of sessions on your IdP to reduce the window for malicious re-use. Limit the amount of SAML Service Providers/Applications used by user accounts with access to Fleet. When removing access to Fleet in the IdP, delete the Fleet user from Fleet as well. For the best resolution, upgrade to Fleet 4.9.1.

Name of the Vulnerable Software and Affected Versions: Redash versions 10.0 and prior Description: Redash is a package for data visualization and sharing. The implementation of URL-loading data sources like JSON, CSV, or Excel in versions 10.0 and prior is vulnerable to advanced methods of Server Side Request Forgery (SSRF). These vulnerabilities are only exploitable on installations where a URL-loading data source is enabled. The `master` and `release/10.x.x` branches address this by applying the Advocate library for making http requests instead of the requests library directly. Recommendations: To resolve the issue, users should upgrade to version 10.0.1 to receive the patch. As a temporary workaround, one can disable the vulnerable data sources entirely by adding an environment variable to the configuration. One can also switch any data source of certain types to be `View Only` for all groups on the Settings > Groups > Data Sources screen. For users unable to update, an admin may modify Redash's configuration through environment variables to mitigate this issue. Depending on the version of Redash, an admin may also need to run a CLI command to re-encrypt some fields in the database. For existing installations, one will need to ensure that explicit values are set for the `REDASH COOKIE SECRET` and `REDASH SECRET KEY` variables.