A few days ago, Google identified a vulnerability in the design of SSL 3.0. This vulnerability allows the plaintext of secure connections to be calculated by a network attacker. This issue was discovered by Bodo Moller in collaboration with Thai Duong and Krzysztof Kotowicz (also Googlers). The attack has been named as the POODLE bites attack, standing for Padding Oracle On Downgraded Legacy Encryption. Check out the document available on the OpenSSL website to learn more about this vulnerability.
What is POODLE?
To maintain compatibility with legacy servers, many TLS clients implement a downgrade dance: in a first handshake attempt, offer the highest protocol version supported by the client; if this handshake fails, they retry (possibly repeatedly) with earlier protocol versions. Unlike proper protocol version negotiation (if the client offers TLS 1.2, the server may respond with, say, TLS 1.0), this downgrade can also be triggered by network glitches, or by active attackers. So if an attacker that controls the network between the client and the server interferes with any attempted handshake offering TLS 1.0 or later, such clients will readily confine themselves to SSL 3.0.
Encryption in SSL 3.0 uses either the RC4 stream cipher, or a block cipher in CBC mode. RC4 is well known to have biases, meaning that if the same secret (such as a password or HTTP cookie) is sent over many connections and thus encrypted with many RC4 streams, more and more information about it will leak.
Unlike with the BEAST and Lucky 13 attacks, there is no reasonable workaround. This leaves us with no secure SSL 3.0 cipher suites at all: to achieve secure encryption, SSL 3.0 must be avoided entirely.
Does POODLE has an impact on cloud environments?
Any system using SSL 3.0 might fall under this attack. Right now, all the Cloud service providers are acting on this vulnerability and updated their customers to close the doors towards the attack.
Amazon AWS Cloud has two public facing services called Elastic Load Balancer (ELB) and Cloud Front, both using the SSLV3 protocol to serve the requests via the secured channel. Generally, the customers themselves will manage the SSL configurations in these two services. To mitigate the POODLE attacks on these two services, we have to disable the SSLV3 Support.
Disable the SSLV3 Protocol to handle POODLE on Amazon AWS ELB
All the ELBs which are created after 10/14/2014 5:00 PM PDT will use a new SSL Negotiation Policy that will by default no longer enable SSLv3.
For the existing ELBs, it’s necessary to manually disable SSLv3 via the AWS Management console:
- Select your load balancer (EC2 -> Load Balancers) in the appropriate region
- In the Listeners tab, click “Change” in the Cipher column.|
- Ensure that the radio button for “Predefined Security Policy” is selected, in the dropdown select the “ELBSecurityPolicy-2014-10” policy. You can see the Protocal-SSLV3 is unchecked after selecting the policy.
- Click “Save” to apply the settings to the listener
- Repeat these steps for each listener that is using HTTPS or SSL for each LoadBalancer.
If you require the SSLv3 support you can re-enable it by selecting the “ELBSecurityPolicy-2014-10” Policy or manually configure the SSL ciphers and protocols as per your requirements. Nevertheless, this will expose you again to POODLE, so you should consider this opportunity very carefully
Disable the SSLv3 Protocol to handle POODLE attacks on Cloud Front
Similarly to ELB, Amazon AWS has taken care of the issue disabling SSLv3 for the customers who uses the default SSL settings. Nevertheless,cCustomers who are using custom SSL certificates with Amazon Cloud Front should disable the SSLv3 protocol manually by following the steps below in the Amazon Cloud Front Management Console:
- Select your distribution, then click “Distribution Settings”.
- Click the “Edit” button on the “General” tab.
- In the “Custom SSL Client Support” section, select the option that says: “Only Clients that Support Server Name Indication (SNI)”.
- Click “Yes, Edit” to save these revised settings.
AWS API endpoints are not affected by the attack described in the POODLE paper. Instead of using cookies to authenticate users, a unique signature is computed for every request. No action is required from customers that use the AWS SDK or other SDKs to access our API endpoints.
WaitCondition Controls the Pace of AWS CloudFormation Templates
AWS's WaitCondition can be used with CloudFormation templates to ensure required resources are running.As you may already be aware, AWS CloudFormation is used for infrastructure automation by allowing you to write JSON templates to automatically install, configure, and bootstrap your ...
The 9 AWS Certifications: Which is Right for You and Your Team?
As companies increasingly shift workloads to the public cloud, cloud computing has moved from a nice-to-have to a core competency in the enterprise. This shift requires a new set of skills to design, deploy, and manage applications in the cloud.As the market leader and most mature p...
Two New EC2 Instance Types Announced at AWS re:Invent 2018 – Monday Night Live
The announcements at re:Invent just keep on coming! Let’s look at what benefits these two new EC2 instance types offer and how these two new instances could be of benefit to you. If you're not too familiar with Amazon EC2, you might want to familiarize yourself by creating your first Am...
Google Cloud Certification: Preparation and Prerequisites
Google Cloud Platform (GCP) has evolved from being a niche player to a serious competitor to Amazon Web Services and Microsoft Azure. In 2018, research firm Gartner placed Google in the Leaders quadrant in its Magic Quadrant for Cloud Infrastructure as a Service for the first time. In t...
Understanding AWS VPC Egress Filtering Methods
In order to understand AWS VPC egress filtering methods, you first need to understand that security on AWS is governed by a shared responsibility model where both vendor and subscriber have various operational responsibilities. AWS assumes responsibility for the underlying infrastructur...
S3 FTP: Build a Reliable and Inexpensive FTP Server Using Amazon’s S3
Is it possible to create an S3 FTP file backup/transfer solution, minimizing associated file storage and capacity planning administration headache?FTP (File Transfer Protocol) is a fast and convenient way to transfer large files over the Internet. You might, at some point, have conf...
Microservices Architecture: Advantages and Drawbacks
Microservices are a way of breaking large software projects into loosely coupled modules, which communicate with each other through simple Application Programming Interfaces (APIs).Microservices have become increasingly popular over the past few years. The modular architectural style,...
What Are Best Practices for Tagging AWS Resources?
There are many use cases for tags, but what are the best practices for tagging AWS resources? In order for your organization to effectively manage resources (and your monthly AWS bill), you need to implement and adopt a thoughtful tagging strategy that makes sense for your business. The...
How to Optimize Amazon S3 Performance
Amazon S3 is the most common storage options for many organizations, being object storage it is used for a wide variety of data types, from the smallest objects to huge datasets. All in all, Amazon S3 is a great service to store a wide scope of data types in a highly available and resil...
How to Optimize Cloud Costs with Spot Instances: New on Cloud Academy
One of the main promises of cloud computing is access to nearly endless capacity. However, it doesn’t come cheap. With the introduction of Spot Instances for Amazon Web Services’ Elastic Compute Cloud (AWS EC2) in 2009, spot instances have been a way for major cloud providers to sell sp...
What are the Benefits of Machine Learning in the Cloud?
A Comparison of Machine Learning Services on AWS, Azure, and Google CloudArtificial intelligence and machine learning are steadily making their way into enterprise applications in areas such as customer support, fraud detection, and business intelligence. There is every reason to beli...
How to Use AWS CLI
The AWS Command Line Interface (CLI) is for managing your AWS services from a terminal session on your own client, allowing you to control and configure multiple AWS services.So you’ve been using AWS for awhile and finally feel comfortable clicking your way through all the services....