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 have 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 CloudFront, 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 Protocol-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 Amazon ELB, Amazon AWS has taken care of the issue disabling SSLv3 for the customers who use the default SSL settings. Nevertheless, customers who are using custom SSL certificates with Amazon Cloud Front should disable the SSLv3 protocol manually by following the steps below in the Amazon CloudFront 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.
How to Unlock Complimentary Access to Cloud Academy
Are you looking to get trained or certified on AWS, Azure, Google Cloud Platform, DevOps, Cloud Security, Python, Java, or another technical skill? Then you'll want to mark your calendars for August 23, 2019. Starting Friday at 12:00 a.m. PDT (3:00 a.m. EDT), Cloud Academy is offering c...
What Exactly Is a Cloud Architect and How Do You Become One?
One of the buzzwords surrounding the cloud that I'm sure you've heard is "Cloud Architect." In this article, I will outline my understanding of what a cloud architect does and I'll analyze the skills and certifications necessary to become one. I will also list some of the types of jobs ...
Boto: Using Python to Automate AWS Services
Boto allows you to write scripts to automate things like starting AWS EC2 instances Boto is a Python package that provides programmatic connectivity to Amazon Web Services (AWS). AWS offers a range of services for dynamically scaling servers including the core compute service, Elastic...
Content Roadmap: AZ-500, ITIL 4, MS-100, Google Cloud Associate Engineer, and More
Last month, Cloud Academy joined forces with QA, the UK’s largest B2B skills provider, and it put us in an excellent position to solve a massive skills gap problem. As a result of this collaboration, you will see our training library grow with additions from QA’s massive catalog of 500+...
DevSecOps: How to Secure DevOps Environments
Security has been a friction point when discussing DevOps. This stems from the assumption that DevOps teams move too fast to handle security concerns. This makes sense if Information Security (InfoSec) is separate from the DevOps value stream, or if development velocity exceeds the band...
Test Your Cloud Knowledge on AWS, Azure, or Google Cloud Platform
Cloud skills are in demand | In today's digital era, employers are constantly seeking skilled professionals with working knowledge of AWS, Azure, and Google Cloud Platform. According to the 2019 Trends in Cloud Transformation report by 451 Research: Business and IT transformations re...
Disadvantages of Cloud Computing
If you want to deliver digital services of any kind, you’ll need to estimate all types of resources, not the least of which are CPU, memory, storage, and network connectivity. Which resources you choose for your delivery — cloud-based or local — is up to you. But you’ll definitely want...
Google Cloud vs AWS: A Comparison (or can they be compared?)
The "Google Cloud vs AWS" argument used to be a common discussion among our members, but is this still really a thing? You may already know that there are three major players in the public cloud platforms arena: Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP)...
Deployment Orchestration with AWS Elastic Beanstalk
If you're responsible for the development and deployment of web applications within your AWS environment for your organization, then it's likely you've heard of AWS Elastic Beanstalk. If you are new to this service, or simply need to know a bit more about the service and the benefits th...
How to Use & Install the AWS CLI
What is the 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 and implement a level of automation. If you’ve been using AWS for some time and feel...
Cloud Academy’s Blog Digest: July 2019
July has been a very exciting month for us at Cloud Academy. On July 10, we officially joined forces with QA, the UK’s largest B2B skills provider (read the announcement). Over the coming weeks, you will see additions from QA’s massive catalog of 500+ certification courses and 1500+ ins...
AWS Fundamentals: Understanding Compute, Storage, Database, Networking & Security
If you are just starting out on your journey toward mastering AWS cloud computing, then your first stop should be to understand the AWS fundamentals. This will enable you to get a solid foundation to then expand your knowledge across the entire AWS service catalog. It can be both d...