CVE-2020-36363
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAmazon 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAmazon AWS CloudFront's TLSv1.2_2019 security policy includes CBC-mode cipher suites (TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 and TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) that are considered weak due to known vulnerabilities in CBC mode and the use of older SHA hash functions, potentially exposing traffic to cryptographic attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.2_2019CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
List CloudFront distributions and viewer TLS policiesUse the AWS CLI command: aws cloudfront list-distributions --query 'DistributionList.Items[*].{Id:Id,Arn:ARN,ViewerCertificate:ViewerCertificate}'Affected if Any distribution shows TLSv1.2_2019 as the minimum TLS version or in the SSLSupportMethod
-
Check the specific TLS security policy configuredRun: aws cloudfront get-distribution-config --id <DISTRIBUTION_ID> --query 'DistributionConfig.ViewerCertificate.MinimumProtocolVersion'Affected if The MinimumProtocolVersion field returns TLSv1.2_2019
-
Inspect custom TLS policies for weak CBC ciphersIf using a custom policy, examine the configured cipher suites using: aws cloudfront list-cloud-front-origin-access-identities (for OAI) or check the SSLSupportMethod configuration. Review whether the policy explicitly includes TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 or TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384Affected if The configured policy contains either TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 or TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 cipher suites
A distribution is affected if it uses TLSv1.2_2019 as the minimum TLS protocol version or has a custom policy that includes the weak CBC-mode cipher suites TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 or TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReconfigure CloudFront distributions to use a stricter TLS security policy that excludes CBC-mode ciphers, such as TLSv1.2_2021 or a custom policy allowing only GCM-based cipher suites.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36363 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-36363 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data