Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

11/5/2009
01:36 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Little-Known Hole Lets Attacker Hit Main Website Domain Via Its Subdomains

Proof-of-concept demonstrates how exploits on Google, Expedia, Chase Manhattan subdomains could lead to compromises of their main sites

Turns out an exploit on a Website's subdomain can be used to attack the main domain: A researcher has released a proof-of-concept showing how cookies can be abused to execute such an insidious attack.

Michael Bailey, senior researcher for Foreground Security, published a paper this week that demonstrates how an exploit in a subdomain, such as mail.google.com, could be used to hack the main production domain, google.com, all because of the way browsers handle cookies.

"There's no specific vulnerability here, but it's widening the attack surface for any large organization that has more than one [Web] server set up. A [vulnerability] in any one of those servers can affect all the rest," Bailey says.

Most Web developers aren't aware that a vulnerability in a subdomain could be used to target the main domain. "We're trying to get the message out that now you have to treat everything [in the domain] as though someone can compromise your crown jewels," says Michael Murray, CSO for Foreground. "You have to realize that every vulnerability, every attack vector in those subdomains, can be used to compromise [other areas of the domain]," he says.

It all boils down to the browsers themselves. Within the DNS architecture, the main domain -- fortune500company.com, for instance -- has control over its subdomains, such as development.fortune500company.com. Development.fortune500company.com has no authority to change anything on the main fortune500company.com site.

But browsers do the reverse, Murray says. Development.fortune500company.com can set cookies for fortune500company.com, the main domain. That leaves the door open for cookie-tampering, he says, when the subdomain has an exploitable vulnerability, such as cross-site scripting (XSS) or cross-site request forgery (CSRF).

"Most developers don't care if there's an XSS bug in the development site. But now all of those vulnerabilities are as important as an XSS in the main site," Murray says.

There's no actual patch to protect against the attack -- it's more about how Web developers set up their site domains. And when the site uses third-party content, it's even more at risk, according to the researchers.

In his paper (PDF), Foreground's Bailey showed PoCs with Google, Expedia, and Chase Manhattan's Websites. "The Chase online banking app could be compromised from one of the marketing companies they partnered with," Bailey says. His example in the PoC showed how images.chase.com, images.capitalone.com, and online.chasevisasignature.com all point to content from images.bigfootinteractive.com, an advertising agency's server. That server is actually vulnerable to XSS, he found, so it can be used to compromise a legitimate Chase user's banking session.

The answer, he says, is to use a completely different subdomain from your main one when pointing to content from a third party.

Bailey says so far he hasn't seen any actual attacks exploiting this. "But I have seen mentions of similar research on black hat forums. I know this isn't completely new to black hats," he says. He recommends users clean up their cookies regularly and use separate Web browsers or browser sessions for sensitive browsing activities.

Meanwhile, any flaw on a subdomain is putting all users on the main domain at risk. "They've got to treat a development site the same as the online banking site," Foreground's Murray says. "The implications are huge here."

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15820
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.
CVE-2020-15821
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, a user without permission is able to create an article draft.
CVE-2020-15823
PUBLISHED: 2020-08-08
JetBrains YouTrack before 2020.2.8873 is vulnerable to SSRF in the Workflow component.
CVE-2020-15824
PUBLISHED: 2020-08-08
In JetBrains Kotlin before 1.4.0, there is a script-cache privilege escalation vulnerability due to kotlin-main-kts cached scripts in the system temp directory, which is shared by all users by default.
CVE-2020-15825
PUBLISHED: 2020-08-08
In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges.