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 Executive Editor at DarkReading.com. 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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
AI Is Everywhere, but Don't Ignore the Basics
Howie Xu, Vice President of AI and Machine Learning at Zscaler,  9/10/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-4147
PUBLISHED: 2019-09-16
IBM Sterling File Gateway 2.2.0.0 through 6.0.1.0 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 158413.
CVE-2019-5481
PUBLISHED: 2019-09-16
Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.
CVE-2019-5482
PUBLISHED: 2019-09-16
Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.
CVE-2019-15741
PUBLISHED: 2019-09-16
An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. An unsafe interaction with logrotate could result in a privilege escalation
CVE-2019-16370
PUBLISHED: 2019-09-16
The PGP signing plugin in Gradle before 6.0 relies on the SHA-1 algorithm, which might allow an attacker to replace an artifact with a different one that has the same SHA-1 message digest, a related issue to CVE-2005-4900.