A new security report is raising alarms about Tailscale’s built-in Tailscale SSH feature. Researchers found a potential privilege escalation issue that could appear during “partial forwarding” workflows. In plain terms: if an attacker already controls a device that’s allowed to log in, they may be able to abuse the SSH forwarding chain to access other servers’ protected services—possibly even reaching the most privileged admin areas. Why this matters: Tailscale helps teams connect dispersed devices into a private, encrypted “Tailnet.” Normally, access is enforced via admin rules—so users can only do what they’re authorized to do. But during testing of Tailscale 1.104.2, the backend component handling SSH appeared to run with highest system privileges, and certain forwarding paths may not properly apply the login account’s permission boundaries. The team demonstrated using SSH forwarding into a Docker-related management service to run high-privilege commands and read protected files. They also noted that without Tailnet Lock enabled, an attacker might obtain keys to add devices to the same Tailnet—though final access is still constrained by the original Tailscale policy. Mitigation: review SSH policies, disable SSH forwarding if not needed, and apply least-privilege. #Tailscale #SecurityResearch #PrivilegeEscalation #SSH #ZeroTrust #DevOps
Want to learn more? Visit Explore the world, stay updated on travel insights and international affairs, and discover authentic stories from real life
评论
发表评论