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.

Cloud Security //

AWS

4/6/2018
09:35 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Don't Call AWS' CloudFront Hijacking Problem a Vulnerability

Amazon Web Service might be the biggest of the big cloud providers, but it still has some security concerns. A researcher has noticed the company is open to having its CloudFront service hijacked, but Amazon officials won't call it a vulnerability.

Amazon Web Services is trying rather hard to get its security game going to the next level. But security researchers keep finding new ways to mess with it.

The newest one is from MindPoint Group, and involves the AWS CloudFront CDN service. Security analyst Matt Westfall found out that in a misconfigured CloudFront account, subdomains of legitimate sites could be hijacked.

This is, at root, a flaw in CloudFront.

While each CloudFront distribution will have a unique endpoint for users to point their DNS records to, all of the domains using a specific distribution must be listed in the "Alternate Domain Names" (CNAMEs) field in the options for that distribution.

However, when the CDN gets a request, it uses the HOST header of the request to determine which distribution to use. In this scenario, if the HOST header does not match an entry in the "Alternate Domain Names" (CNAMEs) field of the intended distribution, the request will fail.

Any other distribution that contains the specific domain in the HOST header will receive the request and respond to it normally. This is the mechanism that enables the hijack to occur.

The binding mechanism that should be in place inside CloudFront is then easily bypassed. A request to one specific CloudFront subdomain will not be limited to only that associated distribution list.

In his blog, Westfall wrote about how he tested out his observation.

What Westfall ended up doing is creating a Python script that would test for misconfiguration and repoint vulnerable subdomains to the target of his choice.

In his test, he ran the script for a few days and found that he had hijacked a lot of high-profile subdomains. They included two distinct US Federal "dot gov" organizations, Bloomberg Businessweek, Commonwealth Bank of Australia, Dow Jones, Harvard University, Red Cross and Reuters.

The problem seemed to be widespread.

The AWS response was interesting.

Westfall discussed what he found out with the AWS Security team and the CloudFront engineers. As he put it, "...while they accept that the nuances of CloudFront's routing mechanism leave room for improvement, at no time have they decided to treat this issue as a vulnerability."


The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth-annual Big Communications Event. There's still time to register and communications service providers get in free!

Huh.

Westfall recommends that "most AWS customers with a single distribution can protect themselves by adding a wildcard domain (such as *.disloops.com) to the "Alternate Domain Names" (CNAMEs) field.

Amazon isn't totally ignoring this, either.

The CloudFront console now displays a popup when a user removes a CNAME from a CloudFront distribution that warns them to keep their DNS records in sync with their CloudFront distribution. Such a synchronization would prevent the possibility of hijacking.

Amazon has been getting more security conscious lately.

At the AWS Summit this week, the cloud provider introduced new automation tools for making secure apps easier to run in AWS. (See AWS Expands Cloud Security Automation.)

Although the company doesn't consider the CloudFront situation a vulnerability, its engineers are trying to help users avoid the situation where it could happen. They seem to have realized that just the selling of runtime on someone else's computer may not be the entire business model that is needed for success.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
Modern Day Insider Threat: Network Bugs That Are Stealing Your Data
David Pearson, Principal Threat Researcher,  10/21/2020
Are You One COVID-19 Test Away From a Cybersecurity Disaster?
Alan Brill, Senior Managing Director, Cyber Risk Practice, Kroll,  10/21/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-21269
PUBLISHED: 2020-10-27
checkpath in OpenRC through 0.42.1 might allow local users to take ownership of arbitrary files because a non-terminal path component can be a symlink.
CVE-2020-27743
PUBLISHED: 2020-10-26
libtac in pam_tacplus through 1.5.1 lacks a check for a failure of RAND_bytes()/RAND_pseudo_bytes(). This could lead to use of a non-random/predictable session_id.
CVE-2020-1915
PUBLISHED: 2020-10-26
An out-of-bounds read in the JavaScript Interpreter in Facebook Hermes prior to commit 8cb935cd3b2321c46aa6b7ed8454d95c75a7fca0 allows attackers to cause a denial of service attack or possible further memory corruption via crafted JavaScript. Note that this is only exploitable if the application usi...
CVE-2020-26878
PUBLISHED: 2020-10-26
Ruckus through 1.5.1.0.21 is affected by remote command injection. An authenticated user can submit a query to the API (/service/v1/createUser endpoint), injecting arbitrary commands that will be executed as root user via web.py.
CVE-2020-26879
PUBLISHED: 2020-10-26
Ruckus vRioT through 1.5.1.0.21 has an API backdoor that is hardcoded into validate_token.py. An unauthenticated attacker can interact with the service API by using a backdoor value as the Authorization header.