CVE-2020-36363

CRITICALNVD 9.89.8—

9.8

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.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 52.0%
KEV: Not listed

Published

August 12, 2021

Last Modified

November 21, 2024

References (4)

cve@mitrehttps://aws.amazon.com/about-aws/whats-new/2020/07/cloudfront-tls-security-policy/
cve@mitrehttps://stackoverflow.com/questions/62071604
af854a3a-2127-422b-91ae-364da2661108https://aws.amazon.com/about-aws/whats-new/2020/07/cloudfront-tls-security-policy/
af854a3a-2127-422b-91ae-364da2661108https://stackoverflow.com/questions/62071604

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-327Use of a Broken or Risky Cryptographic Algorithm

Data Freshness Timeline

(refreshed 10× in last 7d / 19× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 12:06 UTCEG score recompute
2026-05-26 12:06 UTCGHSA enrichment
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-24 14:21 UTCOSV refresh

Frequently asked(5)

What is CVE-2020-36363?

CVE-2020-36363 is a critical vulnerability published on August 12, 2021. Amazon AWS CloudFront TLSv1.22019 allows TLSECDHERSAWITHAES128CBCSHA256 and TLSECDHERSAWITHAES256CBC_SHA384, which some entities consider to be weak ciphers.

When was CVE-2020-36363 disclosed?

CVE-2020-36363 was first published in the National Vulnerability Database on August 12, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-36363 actively exploited?

CVE-2020-36363 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-36363?

CVE-2020-36363 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2020-36363?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-36363, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-36363

Explore →

Is Your Infrastructure Affected by CVE-2020-36363?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2020-36363

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-36363?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)