# CVE-2020-36363: Weak cryptography in n/a

> AWS CloudFront allows weak CBC-mode ciphers in TLSv1.2_2019, potentially enabling cryptographic attacks against encrypted traffic.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mwmh-v67h-98jp

## What is CVE-2020-36363?

CVE-2020-36363 is a critical vulnerability in n/a, published on 12 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2020-36363?

It affects 1 product.


Products: Amazon Amazon Cloudfront.

## How do I fix CVE-2020-36363?

No fix has been published for CVE-2020-36363 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-36363 being exploited?

There is no known exploitation of CVE-2020-36363 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36363 and fix it if it is affected.

What it is: CVE-2020-36363 is a critical vulnerability in n/a, published on 12 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36363 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-36363/ (Markdown: https://insights.sbomify.com/CVE-2020-36363/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-36363
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-36363
- OSV: https://osv.dev/vulnerability/CVE-2020-36363

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-36363/
Summaries are generated and may contain mistakes; the official description above is the record.