Advisory

GHSA-ch68-7cf4-35vr

Also known as: CVE-2022-23600

Summary

Limited ability to spoof SAML authentication with missing audience verification in Fleet

Details

Impact

This impacts deployments using SAML SSO in two specific cases:

  1. A malicious or compromised Service Provider (SP) could reuse the SAML response to log into Fleet as a user -- only if the user has an account with the same email in Fleet, _and_ the user signs into the malicious SP via SAML SSO from the same Identity Provider (IdP) configured with Fleet.
  2. A user with an account in Fleet could reuse a SAML response intended for another SP to log into Fleet. This is only a concern if the user is blocked from Fleet in the IdP, but continues to have an account in Fleet. If the user is blocked from the IdP entirely, this cannot be exploited.

Patches
Fleet 4.9.1 resolves this issue.

Workarounds and good practices

  • 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 more information
If you have any questions or comments about this advisory:

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2022-02-07 21:57 UTC
Modified
2023-11-08 04:08 UTC

Affected packages and fixes

github.com/fleetdm/fleet/v4

Go · All systems

Affected

  • introduced 0, fixed 4.9.1 (semver)

Fixed versions

4.9.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences