ts-2024-012
Vulnerability from tailscale

Description: Tailscale Funnel abused for phishing

What happened?

A malicious user abused Tailscale Funnel to host a phishing page targeting Facebook users. This user created multiple free Tailscale accounts to use as an obfuscation/anonymity proxy for their VPS instance hosting the phishing page.

We received the first report about a phishing page on September 23rd, 2024, and took down the Funnel page the same day. We received the second report on October 1st, 2024, for the same phishing page on a different Tailscale account. We took down the second page, added detection for new similar pages, and repeatedly shut down new attacker accounts as they were created. After a few more attempts, the attacker stopped creating new accounts.

Who was affected?

232 unique IP addresses accessed the attacker's Funnel nodes. Of those, 87 IP addresses made more than one request, suggesting a possible phishing form submission.

What was the impact?

Some Facebook users could have been phished for their credentials. Since Tailscale Funnel proxies can only see encrypted TLS traffic, we cannot confirm whether anyone was successfully phished.

What do I need to do?

Don't use Tailscale Funnel for phishing.

Show details on source website


{
   guidislink: false,
   id: "https://tailscale.com/security-bulletins/#ts-2024-012",
   link: "https://tailscale.com/security-bulletins/#ts-2024-012",
   links: [
      {
         href: "https://tailscale.com/security-bulletins/#ts-2024-012",
         rel: "alternate",
         type: "text/html",
      },
   ],
   published: "Wed, 02 Oct 2024 00:00:00 GMT",
   summary: "<p><strong><em>Description</em></strong>: Tailscale Funnel abused for phishing</p>\n<h4>What happened?</h4>\n<p>A malicious user abused <a href=\"https://tailscale.com/kb/1223/funnel\">Tailscale Funnel</a> to host a phishing page\ntargeting Facebook users. This user created multiple free Tailscale accounts to\nuse as an obfuscation/anonymity proxy for their VPS instance hosting the\nphishing page.</p>\n<p>We received the first report about a phishing page on September 23rd, 2024, and\ntook down the Funnel page the same day. We received the second report on October\n1st, 2024, for the same phishing page on a different Tailscale account. We took\ndown the second page, added detection for new similar pages, and repeatedly\nshut down new attacker accounts as they were created. After a few more\nattempts, the attacker stopped creating new accounts.</p>\n<h4>Who was affected?</h4>\n<p>232 unique IP addresses accessed the attacker's Funnel nodes. Of those, 87 IP addresses made more\nthan one request, suggesting a possible phishing form submission.</p>\n<h4>What was the impact?</h4>\n<p>Some Facebook users could have been phished for their credentials. Since\nTailscale Funnel proxies can only see encrypted TLS traffic, we cannot confirm\nwhether anyone was successfully phished.</p>\n<h4>What do I need to do?</h4>\n<p>Don't use Tailscale Funnel for phishing.</p>",
   summary_detail: {
      base: "https://tailscale.com/security-bulletins/index.xml",
      language: null,
      type: "text/html",
      value: "<p><strong><em>Description</em></strong>: Tailscale Funnel abused for phishing</p>\n<h4>What happened?</h4>\n<p>A malicious user abused <a href=\"https://tailscale.com/kb/1223/funnel\">Tailscale Funnel</a> to host a phishing page\ntargeting Facebook users. This user created multiple free Tailscale accounts to\nuse as an obfuscation/anonymity proxy for their VPS instance hosting the\nphishing page.</p>\n<p>We received the first report about a phishing page on September 23rd, 2024, and\ntook down the Funnel page the same day. We received the second report on October\n1st, 2024, for the same phishing page on a different Tailscale account. We took\ndown the second page, added detection for new similar pages, and repeatedly\nshut down new attacker accounts as they were created. After a few more\nattempts, the attacker stopped creating new accounts.</p>\n<h4>Who was affected?</h4>\n<p>232 unique IP addresses accessed the attacker's Funnel nodes. Of those, 87 IP addresses made more\nthan one request, suggesting a possible phishing form submission.</p>\n<h4>What was the impact?</h4>\n<p>Some Facebook users could have been phished for their credentials. Since\nTailscale Funnel proxies can only see encrypted TLS traffic, we cannot confirm\nwhether anyone was successfully phished.</p>\n<h4>What do I need to do?</h4>\n<p>Don't use Tailscale Funnel for phishing.</p>",
   },
   title: "TS-2024-012",
   title_detail: {
      base: "https://tailscale.com/security-bulletins/index.xml",
      language: null,
      type: "text/plain",
      value: "TS-2024-012",
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.