ts-2024-001
Vulnerability from tailscale
Description: On Windows before Tailscale version 1.52 and on Linux before
Tailscale 1.54, the tailscale serve
and tailscale funnel
features allowed
users to serve the contents of directories that their user account could not
access, but which the tailscaled
service process could.
What happened?
A user could escalate their own file read access by running, for example,
tailscale.exe serve http / C:\
, and then browsing to the local HTTP endpoint.
The issue can also occur on Linux if the local administrator enabled an operator
user ID with tailscale up --operator=$USER
, as the $USER
account could
serve
itself files that it could not normally read.
Who is affected?
Owners of Windows deployments for which the users of Tailscale nodes do not also
have OS-level administrative access, and owners of Linux deployments where the
administrator enabled non-root --operator
access.
This issue can only be triggered by a local user and cannot be triggered remotely.
What is the impact?
This issue enables local privilege escalation (file read access). Access to
certain system files (such as /etc/shadow
on Linux) can then be used to obtain
full administrative control over the host.
What do I need to do?
On Windows 10 and later, upgrade to Tailscale 1.52 (released 30 October 2023) or later, which resolves the issue.
On Windows 7 and 8, upgrade to Tailscale 1.44.3 (released 8 Jan 2024), which resolves the issue.
On Linux, upgrade to 1.54 (released 15 November 2023) or later, which resolves the issue.
The best practice is to run the latest stable version, which as of this writing is 1.56.1. Consider turning on automatic updates.
Use Tailscale ACLs to control the availability of Funnel.
Show details on source website{ guidislink: false, id: "https://tailscale.com/security-bulletins/#ts-2024-001", link: "https://tailscale.com/security-bulletins/#ts-2024-001", links: [ { href: "https://tailscale.com/security-bulletins/#ts-2024-001", rel: "alternate", type: "text/html", }, ], published: "Mon, 08 Jan 2024 00:00:00 GMT", summary: "<p><strong><em>Description</em></strong>: On Windows before Tailscale version 1.52 and on Linux before\nTailscale 1.54, the <code>tailscale serve</code> and <code>tailscale funnel</code> features allowed\nusers to serve the contents of directories that their user account could not\naccess, but which the <code>tailscaled</code> service process could.</p>\n<h5>What happened?</h5>\n<p>A user could escalate their own file read access by running, for example,\n<code>tailscale.exe serve http / C:\\</code>, and then browsing to the local HTTP endpoint.</p>\n<p>The issue can also occur on Linux if the local administrator enabled an operator\nuser ID with <code>tailscale up --operator=$USER</code>, as the <code>$USER</code> account could\n<code>serve</code> itself files that it could not normally read.</p>\n<h5>Who is affected?</h5>\n<p>Owners of Windows deployments for which the users of Tailscale nodes do not also\nhave OS-level administrative access, and owners of Linux deployments where the\nadministrator enabled non-root <code>--operator</code> access.</p>\n<p>This issue can only be triggered by a local user and cannot be triggered\nremotely.</p>\n<h5>What is the impact?</h5>\n<p>This issue enables local privilege escalation (file read access). Access to\ncertain system files (such as <code>/etc/shadow</code> on Linux) can then be used to obtain\nfull administrative control over the host.</p>\n<h5>What do I need to do?</h5>\n<p>On Windows 10 and later, upgrade to Tailscale 1.52 (<a href=\"https://tailscale.com/changelog#2023-10-30-client\">released 30 October\n2023</a>) or later, which resolves the issue.</p>\n<p>On Windows 7 and 8, upgrade to Tailscale 1.44.3 (<a href=\"https://tailscale.com/changelog#2024-01-08-client\">released 8 Jan\n2024</a>), which resolves the issue.</p>\n<p>On Linux, upgrade to 1.54 (<a href=\"https://tailscale.com/changelog#2023-11-15-client\">released 15 November 2023</a>) or later,\nwhich resolves the issue.</p>\n<p>The best practice is to run the latest stable version, which as of this writing\nis <a href=\"https://tailscale.com/changelog#2023-12-15-client\">1.56.1</a>. Consider turning on <a href=\"https://tailscale.com/blog/auto-update-beta\">automatic updates</a>.</p>\n<p>Use <a href=\"https://tailscale.com/kb/1223/funnel\">Tailscale ACLs</a> to control the availability of Funnel.</p>", summary_detail: { base: "https://tailscale.com/security-bulletins/index.xml", language: null, type: "text/html", value: "<p><strong><em>Description</em></strong>: On Windows before Tailscale version 1.52 and on Linux before\nTailscale 1.54, the <code>tailscale serve</code> and <code>tailscale funnel</code> features allowed\nusers to serve the contents of directories that their user account could not\naccess, but which the <code>tailscaled</code> service process could.</p>\n<h5>What happened?</h5>\n<p>A user could escalate their own file read access by running, for example,\n<code>tailscale.exe serve http / C:\\</code>, and then browsing to the local HTTP endpoint.</p>\n<p>The issue can also occur on Linux if the local administrator enabled an operator\nuser ID with <code>tailscale up --operator=$USER</code>, as the <code>$USER</code> account could\n<code>serve</code> itself files that it could not normally read.</p>\n<h5>Who is affected?</h5>\n<p>Owners of Windows deployments for which the users of Tailscale nodes do not also\nhave OS-level administrative access, and owners of Linux deployments where the\nadministrator enabled non-root <code>--operator</code> access.</p>\n<p>This issue can only be triggered by a local user and cannot be triggered\nremotely.</p>\n<h5>What is the impact?</h5>\n<p>This issue enables local privilege escalation (file read access). Access to\ncertain system files (such as <code>/etc/shadow</code> on Linux) can then be used to obtain\nfull administrative control over the host.</p>\n<h5>What do I need to do?</h5>\n<p>On Windows 10 and later, upgrade to Tailscale 1.52 (<a href=\"https://tailscale.com/changelog#2023-10-30-client\">released 30 October\n2023</a>) or later, which resolves the issue.</p>\n<p>On Windows 7 and 8, upgrade to Tailscale 1.44.3 (<a href=\"https://tailscale.com/changelog#2024-01-08-client\">released 8 Jan\n2024</a>), which resolves the issue.</p>\n<p>On Linux, upgrade to 1.54 (<a href=\"https://tailscale.com/changelog#2023-11-15-client\">released 15 November 2023</a>) or later,\nwhich resolves the issue.</p>\n<p>The best practice is to run the latest stable version, which as of this writing\nis <a href=\"https://tailscale.com/changelog#2023-12-15-client\">1.56.1</a>. Consider turning on <a href=\"https://tailscale.com/blog/auto-update-beta\">automatic updates</a>.</p>\n<p>Use <a href=\"https://tailscale.com/kb/1223/funnel\">Tailscale ACLs</a> to control the availability of Funnel.</p>", }, title: "TS-2024-001", title_detail: { base: "https://tailscale.com/security-bulletins/index.xml", language: null, type: "text/plain", value: "TS-2024-001", }, }
Log in or create an account to share your comment.
This schema specifies the format of a comment related to a security advisory.
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.