<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tiger Huang on Medium]]></title>
        <description><![CDATA[Stories by Tiger Huang on Medium]]></description>
        <link>https://medium.com/@tigerhuangtw?source=rss-126f20e3267c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZEf8gfVBbPt-V90j307Npg.png</url>
            <title>Stories by Tiger Huang on Medium</title>
            <link>https://medium.com/@tigerhuangtw?source=rss-126f20e3267c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:38:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tigerhuangtw/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A Google Cloud Misconfiguration Exposed Critical Internet Exchange Infrastructure]]></title>
            <link>https://tigerhuangtw.medium.com/a-google-cloud-misconfiguration-exposed-critical-internet-exchange-infrastructure-72c4912570b0?source=rss-126f20e3267c------2</link>
            <guid isPermaLink="false">https://medium.com/p/72c4912570b0</guid>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[internet-exchange]]></category>
            <category><![CDATA[google-cloud]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Tiger Huang]]></dc:creator>
            <pubDate>Mon, 26 May 2025 06:28:45 GMT</pubDate>
            <atom:updated>2025-06-17T15:12:18.574Z</atom:updated>
            <content:encoded><![CDATA[<p>A misconfiguration allowed virtual machines globally to reach internal IXP networks — here’s why that matters for the core infrastructure of the Internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8X45iAqF2cmBgpehCqg9Dw.png" /><figcaption>Image generated by AI</figcaption></figure><h3><strong>TL;DR</strong></h3><p>In a recent discovery, I found that <strong>Google Cloud inadvertently exposed subnetworks used for member exchanges at Internet Exchange Points (IXPs)</strong>. Due to this misconfiguration, Google Cloud’s computing infrastructure inadvertently allowed unauthorized access to internal IXP LANs.</p><p>Such access poses serious risks — including unauthorized device access within IXPs, potential zero-day attacks, and the possibility of chaining this into broader multi-vector campaigns. The issue highlights how critical infrastructure can be unintentionally exposed due to cloud route leakage.</p><h3>What Are IXPs?</h3><p>Internet Exchange Points (IXPs) are physical facilities where Internet Service Providers (ISPs), cloud providers, and content networks interconnect to exchange traffic efficiently. IXPs improve performance, reduce latency, and lower costs by enabling direct traffic exchange.</p><p>Participants connect to a shared Layer 2 LAN at the IXP and use the Border Gateway Protocol (BGP) to announce and exchange routing information. Interface speeds typically range from 1 Gigabit to 800 Gigabits. In Taiwan, prominent IXPs include <strong>TPIX, TWIX, STUIX, and FOX IX </strong>— the first three of which were affected by this issue. FOX IX was not impacted because Google is not connected to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dxbNY9ay2TXmLYfRpqP_BA.png" /></figure><h3>What Happened?</h3><p>During our investigation, I discovered that virtual machines deployed on <strong>Google Cloud Compute Engine</strong> could access IXP LANs — subnets that should have remained isolated from any public-facing infrastructure.</p><p>This exposure likely stemmed from <strong>improper route filtering</strong> within Google Cloud’s infrastructure, allowing Google Cloud Compute Engine to reach IXP LAN IP ranges directly. According to PeeringDB (July 2024), <strong>Google is connected to 223 IXPs globally</strong> — of which I found <strong>60 were vulnerable</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oFDKjzJ9lj4F4UHmzEB8Xg.png" /><figcaption>Unexpected access to TWIX Route Server from Google Cloud</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yi_h45EZ6CDTobWF7ZySXw.png" /><figcaption>Reach the TPIX Route Server from Google Cloud</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kLX1-fWrQNISuVDM5ApYhw.png" /><figcaption>Reach the STUIX Route Server from Google Cloud</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nh-c_RFXCgHaZYx-t3f-TA.png" /><figcaption>Reach the Cisco Umbrella (OpenDNS) Router at JPNAP Tokyo from Google Cloud</figcaption></figure><p>While cloud providers often establish direct links with IXPs to improve service latency, in this case, the cloud’s role as a “trusted edge” unintentionally exposed internal IXP routes — a serious security oversight.</p><h3>Disclosure Timeline</h3><ul><li><strong>July 7, 2024</strong> — The vulnerability <strong>was reported</strong> to Google via their Vulnerability Reward Program.</li><li><strong>July 13, 2024</strong> — Google <strong>confirmed</strong> the vulnerability, classified it as P1/S1 (Priority 1 / Severity 1), and <strong>began</strong> working on a fix.</li><li><strong>May 26, 2025</strong> — Google <strong>confirmed</strong> that the vulnerability <strong>had been fully patched</strong> and resolved.</li></ul><h3>Why This Matters</h3><p>IXPs are the backbone of the global Internet. If attackers gain access to these networks:</p><ul><li>They can scan or exploit internal devices within IXPs</li><li>Conduct denial-of-service attacks with little visibility</li><li>Use cloud scale to perform stealthy and distributed operations</li></ul><p>Given the scale at which IXPs operate — often <strong>handling terabytes per second</strong> — malicious traffic in the <strong>gigabyte range</strong> could easily evade detection.</p><p>Cloud platforms offer attackers the ability to spin up resources globally. If targeted, attackers could exploit this path to conduct reconnaissance, or region-specific outages.</p><h3>Responsible Disclosure</h3><p>I submitted the vulnerability to Google, and they confirmed it as valid and patched it on May 26, 2025. Though it didn’t qualify for a bounty, it was acknowledged in the <a href="https://bughunters.google.com/leaderboard/honorable-mentions"><strong>Google Bug Hunters Honorable Mentions</strong></a><strong> </strong>and publicly disclosed here: <a href="https://bughunters.google.com/reports/vrp/uo9yFN1Jd"><strong>Google Bug Hunters Report</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72c4912570b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>