=====================================================================

                             CERT-Renater

                   Note d'Information No. 2021/VULN065
_____________________________________________________________________

DATE                : 08/02/2022

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running Fleet versions prior to 4.9.1,
                                           3.7.0.

=====================================================================
https://github.com/fleetdm/fleet/security/advisories/GHSA-ch68-7cf4-35vr
https://github.com/fleetdm/fleet/security/advisories/GHSA-xwh8-9p3f-3x45
_____________________________________________________________________


Limited ability to spoof SAML authentication with missing audience
verification
Moderate	zwass published GHSA-ch68-7cf4-35vr

Package              github.com/fleetdm/fleet (go)
Affected versions    <= 4.9.0
Patched versions     4.9.1


Description

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.


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:

Join us in the #fleet channel of osquery Slack.
Email us at security@fleetdm.com.


CVE ID
CVE-2022-23600

CWEs
CWE-284 CWE-287

Credits
@iangcarroll iangcarroll Ian Carroll

_____________________________________________________________________

Possible DoS by authorized nodes in live query write
Low	zwass published GHSA-xwh8-9p3f-3x45

Package             No package listed
Affected versions   <= 3.6.0
Patched versions    3.7.0


Description

Impact
A malicious actor with a valid node key can send a badly formatted
request that causes the Fleet server to exit, resulting in denial of
service. This is possible only while a live query is currently ongoing.

We believe the impact of this vulnerability to be low given the
requirement that the actor has a valid node key. There is no information
disclosure, privilege escalation, or code execution.


Patches
The issue is fixed in Fleet 3.7.0.


Workarounds
If this attack is detected, revoke the node key (by deleting the
associated host) that is being used to carry out the attack.


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 security@fleetdm.com.


CVE ID
CVE-2021-21296

Credits
@dsbaha dsbaha

=========================================================
+ CERT-RENATER        |    tel : 01-53-94-20-44         +
+ 23/25 Rue Daviel    |    fax : 01-53-94-20-41         +
+ 75013 Paris         |   email:cert@support.renater.fr +
=========================================================