tailscale.com
Affected
- introduced
1.34.0, fixed1.38.2(semver)
Fixed versions
1.38.2
Fix
- Fixed version
1.38.2go get [email protected]
Advisory
Also known as: CVE-2023-28436, GO-2023-1671
Non-interactive Tailscale SSH sessions on FreeBSD may use the effective group ID of the tailscaled process
A vulnerability identified in the implementation of Tailscale SSH in FreeBSD allowed commands to be run with a higher privilege group ID than that specified by Tailscale SSH access rules.
Affected platforms: FreeBSD
Patched Tailscale client versions: v1.38.2 or later
What happened?
A difference in the behavior of the FreeBSD setgroups system call from POSIX meant that the Tailscale client running on a FreeBSD-based operating system did not appropriately restrict groups on the host when using Tailscale SSH. When accessing a FreeBSD host over Tailscale SSH, the egid of the tailscaled process was used instead of that of the user specified in Tailscale SSH access rules.
Who is affected?
9 tailnets with 22 FreeBSD nodes running Tailscale SSH since Tailscale v1.34 (released on 2022-12-04) may have had Tailscale SSH sessions with a higher privilege group ID than that specified in Tailscale SSH access rules.
We have notified the affected organizations where we have security contacts.
What is the impact?
Tailscale SSH commands may have been run with a higher privilege group ID than that specified in Tailscale SSH access rules if they met all of the following criteria:
What do I need to do?
If you are running Tailscale on FreeBSD, upgrade to v1.38.2 or later to remediate the issue. Admins of a tailnet can view FreeBSD nodes with unpatched versions in the admin console.
To update the local ports tree in advance of what's available upstream, you can:
cd /usr/ports/security/tailscalePORTVERSION to 1.38.2make makesummake installTailscale SSH on other platforms is not affected.
Credits
We would like to thank Ryan Belgrave for reporting this issue.
References
Medium Basis: The source's own band: MODERATE
1.34.0, fixed 1.38.2 (semver)1.38.2
1.38.2go get [email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0