13.07.2015 Views

The Collateral Damage of Internet Censorship by DNS Injection

The Collateral Damage of Internet Censorship by DNS Injection

The Collateral Damage of Internet Censorship by DNS Injection

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>The</strong> <strong>Collateral</strong> <strong>Damage</strong> <strong>of</strong><strong>Internet</strong> <strong>Censorship</strong> <strong>by</strong> <strong>DNS</strong><strong>Injection</strong>Anonymous presented <strong>by</strong> Philip Levis1


Basic Summary• Great Firewall <strong>of</strong> China injects <strong>DNS</strong>responses to restrict access to domain names• This affects traffic originating outside China‣ 26.4% <strong>of</strong> open resolvers affected‣ .de is the most affected TLD (70% <strong>of</strong> open resolvers in kr)• Explain how, where, and why this happens• Present several possible solutionsSIGCOMM 20122


Just To Be ClearThis talk assumes that the Great Firewall <strong>of</strong>China is not designed to restrict <strong>Internet</strong>access to computers outside <strong>of</strong> China.“<strong>Collateral</strong> damage” means restricting accessto computers outside China.SIGCOMM 20123


<strong>DNS</strong> Overviewroot.top level domain (TLD).com, .edu, .cn, .de<strong>Internet</strong>domain (authoritative)stanford.edu, baidu.cnwww.stanford.edu?clientresolverSIGCOMM 2012171.53.10.44


<strong>DNS</strong> <strong>Injection</strong><strong>DNS</strong> serverCensoringASwww.youtube.com?resolverSIGCOMM 2012client5


<strong>DNS</strong> <strong>Injection</strong><strong>DNS</strong> serverCensoringAS<strong>DNS</strong> injectorwww.youtube.com?resolverSIGCOMM 2012client6


<strong>DNS</strong> <strong>Injection</strong><strong>DNS</strong> server<strong>DNS</strong> injectorCensoringASlemon IPresolverSIGCOMM 2012client7


<strong>DNS</strong> <strong>Injection</strong><strong>DNS</strong> serverCensoringAS<strong>DNS</strong> injectorTypically affects both inboundand outbound querieslemon IPresolverSIGCOMM 2012client8


<strong>DNS</strong> <strong>Injection</strong><strong>DNS</strong> serverCensoringAS<strong>DNS</strong> injectorTypically affects both inboundand outbound queries.lemon IPresolverSIGCOMM 2012client9Typically does not suppress“correct” response, just winsrace to respond.


Methodology• HoneyQueries to detect autonomous systemspaths to whom see <strong>DNS</strong> injection• TraceQueries to identify location <strong>of</strong> injectorson affected paths• StepNXQueries to measure collateral damage<strong>of</strong> <strong>DNS</strong> injectionSIGCOMM 201210


HoneyQuery• HoneyQuery: <strong>DNS</strong> query to sensitivedomains, sent to unresponsive IP‣ Assumption: all observed <strong>DNS</strong> responses are from <strong>DNS</strong>injectors• Send from a single vantage point (AS 40676)‣ 14 million IPs that cover all /24 subnets‣ Paths spread to discover all injecting autonomous systems• Record IPs in responses: lemon IPsSIGCOMM 201211


Probed Domain NamesDomainwww.google.comwww.facebook.comwww.twitter.comwww.youtube.comwww.yahoo.comwww.appspot.comwww.xxx.comwww.urltrends.comwww.live.comwww.wikipedia.comCategorySearch EngineSocial NetworkSocial NetworkStreaming MediaPortalWeb HostingPornographySite RankingPortalReferenceSIGCOMM 201212


Blacklisted DomainsDomainwww.google.comwww.facebook.comwww.twitter.comwww.youtube.comwww.yahoo.comwww.appspot.comwww.xxx.comwww.urltrends.comwww.live.comwww.wikipedia.comCategorySearch EngineSocial NetworkSocial NetworkStreaming MediaPortalWeb HostingPornographySite RankingPortalReferenceSIGCOMM 201213


HoneyQuery Results• 28 lemon IPs found‣ Use later to detect injected responses• 388,988 (2.7%) <strong>of</strong> HoneyQueries responded‣ Use to generate poisoned path listSIGCOMM 2012Destination Count PercentageCN 388,206 99.80%CA 363 0.09%US 127 0.03%HK 111 0.03%IN 94 0.02%Top 5 <strong>of</strong> 16 regions• Why are paths to IP addresses outside <strong>of</strong>China experiencing <strong>DNS</strong> injection?14


TraceQuery• For each IP address in the poisoned path list,send a <strong>DNS</strong> query to a blacklisted domainwith increasing TTL‣ Queries which reach an injector will trigger a response• Mark IP address and autonomous system <strong>of</strong>router for TTL that triggers response‣ Sometimes queries trigger multiple responses, from multipleinjectorsSIGCOMM 201215


Examplewww.facebook.com?AS1AS2AS3AS4SIGCOMM 201216


Examplewww.facebook.com?AS1AS2AS3AS4SIGCOMM 201217


Examplelemon IPAS1AS2AS3AS4SIGCOMM 201218


Examplelemon IPAS1AS2AS3AS4SIGCOMM 201219


Examplelemon IP, lemon IPAS1AS2AS3AS4SIGCOMM 201220


Examplelemon IP, lemon IP,good IPAS1AS2AS3AS4SIGCOMM 201221


Examplelemon IP, lemon IP,good IPAS1AS2Injector AAS3Injector BAS4SIGCOMM 201222


TraceQuery Results• Found 3,120 router IP addresses associatedwith <strong>DNS</strong> injection• All 3,120 IP addresses belong to 39 Chineseautonomous systemsSIGCOMM 2012AS Name AS Number IPsChinanet 4134 1952CNCGroup China169 Backbone 4837 489China Telecom (Group) 4812 289CHINA RAILWAY <strong>Internet</strong> (CRNEt) 9394 78China Netcom Corp. 9929 67Top 5 ASes <strong>by</strong> router IP count• How much does this affect the <strong>Internet</strong>?23


Methodology• Tested 43,842 open <strong>DNS</strong> resolvers in 173countries outside <strong>of</strong> China‣ List from probing <strong>DNS</strong> servers <strong>of</strong> Alexa 1M top websites‣ Supplemented <strong>by</strong> lists from researchers• Query for blacklisted domain from vantagepoint, check if response is lemon IP‣ Test blacklisted name for all 312 TLDs‣ Also, check against TCP-based <strong>DNS</strong> queries (injectors donot target <strong>DNS</strong> queries over TCP)SIGCOMM 201224


StepNX Query• To identify where injection occurs, injectrandom strings into domain name‣ Injectors use very liberal pattern matching‣ Generate invalid names, expect NXDOMAIN response‣ www.facebook.com.{INVALID}: path to root server‣ www.facebook.com.{INVALID}.com: path to TLD server‣ Repeat 200 times to try different servers/paths<strong>DNS</strong> Level Affected Resolvers Affected RateRoot 1 0.002%TLD 11573 26.4%Authoritative 99 0.23%Which resolution step sees injectionSIGCOMM 201225


StepNX Query• To identify where injection occurs, injectrandom strings into domain name‣ Injectors use very liberal pattern matching‣ Generate invalid names, expect NXDOMAIN response‣ www.facebook.com.{INVALID}: path to root server‣ www.facebook.com.{INVALID}.com: path to TLD server‣ Repeat 200 times to try different servers/paths<strong>DNS</strong> Level Affected Resolvers Affected RateRoot 1 0.002%TLD 11573 26.4%Authoritative 99 0.23%Which resolution step sees injectionSIGCOMM 201226


Who’s Affected?• 3 TLDs affected almostcompletely (99.53%)‣ cn, xn--fiqs8s, xn--fiqz9s‣ Expected: domains from withinGreat Firewall <strong>of</strong> China• 11,573 (26.4%) <strong>of</strong>resolvers affected for oneor more <strong>of</strong> 16unexpected TLDsSIGCOMM 201227TLD Affected Resolversde 8192xn--3e0b707e 5641kr 4842kp 384co 90travel 90pl 90no 90iq 90hk 90fi 90uk 90xn--j6w193g 90jp 90nz 90ca 9016 unexpected TLDs affected <strong>by</strong> <strong>DNS</strong>injection on path from an open resolver


Whose Resolvers?Open resolvers in 109 regions affectedRegion Affected Resolvers PercentageIran 157 88%Myanmar 163 85%Korea 198 79%Hong Kong 403 75%Taiwan 1146 66%India 250 60%Top 6 regions <strong>by</strong> affected open resolver percentageSIGCOMM 201228


Details: .deRegionResolvers Affectedkr 76%my 66%hk 54%ar 44%il 42%ir 36%tw 36%bg 31%jp 28%ro 25%10 regions whose open resolvers aremost greatly affected for .de queriesSIGCOMM 201229


nic.de,194.0.0.53) goes through a censoring AS (AS7497)in China, which is the cause <strong>of</strong> the collateral damage on thisresolver. We show the AS path in Figure 5: 39737, 6939,10026, 7497, 24151, 31529.Example .de <strong>Injection</strong>AS3549(GBLX GlobalCrossing, US)AS3356(LEVEL3,US)AS 1280(ISC, US)AS4847CNIX-APAS9700KRNIC-AS-KRAS4635HKIX-RS1 HKAS4641ASN-CUHKNETHKAS 24151CNNIC CRITICAL-AP(CN)AS8763 DENIC-AS DENIC eGDEAS 10026PacnetGlobal (HK)AS7497CSTNET-AS-AP(CN)AS 6939HurricaneElectric (US)AS 39737Net VisionTelcom SRL(RO)ASes inChina...AS 24136CNNIC-APAS 23596E<strong>DNS</strong>KR1 NIDAKRAS 31529DENIC eG(DE)SIGCOMM 201230Figure 5: Topology <strong>of</strong> ASes neighboring CNNIC


nic.de,194.0.0.53) goes through a censoring AS (AS7497)in China, which is the cause <strong>of</strong> the collateral damage on thisresolver. We show the AS path in Figure 5: 39737, 6939,10026, 7497, 24151, 31529.Example .de <strong>Injection</strong>AS3549(GBLX GlobalCrossing, US)AS3356(LEVEL3,US)AS 1280(ISC, US)AS4847CNIX-APAS9700KRNIC-AS-KRAS4635HKIX-RS1 HKAS4641ASN-CUHKNETHKAS 24151CNNIC CRITICAL-AP(CN)AS8763 DENIC-AS DENIC eGDEAS 10026PacnetGlobal (HK)AS7497CSTNET-AS-AP(CN)AS 6939HurricaneElectric (US)AS 39737Net VisionTelcom SRL(RO)ASes inChina...AS 24136CNNIC-APAS 23596E<strong>DNS</strong>KR1 NIDAKRAS 31529DENIC eG(DE)SIGCOMM 201231Figure 5: Topology <strong>of</strong> ASes neighboring CNNIC


nic.de,194.0.0.53) goes through a censoring AS (AS7497)in China, which is the cause <strong>of</strong> the collateral damage on thisresolver. We show the AS path in Figure 5: 39737, 6939,10026, 7497, 24151, 31529.Example .de <strong>Injection</strong>AS3549(GBLX GlobalCrossing, US)AS3356(LEVEL3,US)AS 1280(ISC, US)AS4847CNIX-APAS9700KRNIC-AS-KRAS4635HKIX-RS1 HKAS4641ASN-CUHKNETHKAS 24151CNNIC CRITICAL-AP(CN)AS8763 DENIC-AS DENIC eGDEAS 10026PacnetGlobal (HK)AS7497CSTNET-AS-AP(CN)AS 6939HurricaneElectric (US)AS 39737Net VisionTelcom SRL(RO)ASes inChina...AS 24136CNNIC-APAS 23596E<strong>DNS</strong>KR1 NIDAKRAS 31529DENIC eG(DE)SIGCOMM 201232Figure 5: Topology <strong>of</strong> ASes neighboring CNNIC


Solutions• <strong>DNS</strong> injectors could filter out transit queries• Autonomous systems could avoid transitthrough injecting neighbors‣ Particularly, TLD operators could monitor peering paths• Security extensions for <strong>DNS</strong> (<strong>DNS</strong>SEC)prevent injection‣ <strong>DNS</strong>SEC has signed responses‣ Resolvers would reject injected responses, accept slowerones from authoritative servers‣ .de and .kr both support <strong>DNS</strong>SECSIGCOMM 201233


Conclusion• Great Firewall <strong>of</strong> China’s <strong>DNS</strong> injection isaffecting lookups originating outside China‣ Caused <strong>by</strong> queries traversing Chinese ASes‣ Effect is greatest at routes between resolvers and TLDs• Suggestions on preventing collateral damage• Some recent changes...SIGCOMM 201234


Questionsplease contactAnonymous

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!