CVE-2020-36363
First published: Thu Aug 12 2021(Updated: )
Amazon AWS CloudFront TLSv1.2_2019 allows TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 and TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, which some entities consider to be weak ciphers.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Amazon CloudFront | =1.2_2019 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-36363?
CVE-2020-36363 is considered to have a medium severity due to the use of weak cryptographic ciphers in Amazon AWS CloudFront.
How do I fix CVE-2020-36363?
To mitigate CVE-2020-36363, configure your Amazon CloudFront distribution to use stronger TLS ciphers and protocols.
What vulnerable components are affected by CVE-2020-36363?
The vulnerable component affected by CVE-2020-36363 is Amazon CloudFront version 1.2_2019.
What are the implications of exploiting CVE-2020-36363?
Exploiting CVE-2020-36363 could allow attackers to compromise encrypted traffic due to the use of weak ciphers.
Is there a workaround for CVE-2020-36363?
A workaround for CVE-2020-36363 is to disable weak ciphers in your AWS CloudFront configuration until a fix can be applied.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/amazon
- canonical/amazon cloudfront
- version/amazon cloudfront/1.2_2019