Summary
Limited ability to spoof SAML authentication with missing audience verification in Fleet
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:
- Join us in the #fleet channel of osquery Slack.
- Email us at [email protected].
Impact
This impacts 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 -- 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.
- 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.
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
CVE-2022-23600 has a CVSS score of 5.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.9.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Fleet 4.9.1 resolves this issue.
Frequently Asked Questions
- What is CVE-2022-23600? CVE-2022-23600 is a medium-severity improper authentication vulnerability in github.com/fleetdm/fleet/v4 (go), affecting versions < 4.9.1. It is fixed in 4.9.1. The application does not adequately verify the identity of a user, device, or process before granting access.
- How severe is CVE-2022-23600? CVE-2022-23600 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/fleetdm/fleet/v4 are affected by CVE-2022-23600? github.com/fleetdm/fleet/v4 (go) versions < 4.9.1 is affected.
- Is there a fix for CVE-2022-23600? Yes. CVE-2022-23600 is fixed in 4.9.1. Upgrade to this version or later.
- Is CVE-2022-23600 exploitable, and should I be worried? Whether CVE-2022-23600 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-23600 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-23600? Upgrade
github.com/fleetdm/fleet/v4to 4.9.1 or later.