Security readout for executives and security teams
Plain-English summary
CVE-2020-36421 is a side-channel weakness in Arm Mbed TLS before 2.23.0. Under the described condition, RSA private keys used inside a secure enclave could be disclosed. The business concern is confidentiality of private keys in embedded, appliance, or application environments that embed vulnerable Mbed TLS versions.
Executive priority
Treat as a targeted confidentiality risk, not an emergency mass-exploitation issue based on current evidence. Prioritize environments protecting long-lived RSA private keys, embedded products, and customer-facing systems with bundled Mbed TLS.
Technical view
The issue is tied to modular exponentiation behavior and is classified as CWE-203. The CVSS 3.1 score is 5.3, with network attack vector, low complexity, no privileges, and confidentiality-only impact. Public bundle data identifies Mbed TLS before 2.23.0 and references Arm release and issue materials.
Likely exposure
Most likely exposure is software, firmware, appliances, or services bundling Arm Mbed TLS before 2.23.0, especially where RSA private-key operations occur in secure enclave contexts. The source bundle does not enumerate specific affected products or CPEs.
Exploitation context
CISA KEV status is false, and the provided sources do not state active exploitation. The available evidence describes a side-channel disclosure risk, but does not provide exploit maturity, public exploitation, or product-specific attack scenarios.
Researcher notes
The source bundle gives the vulnerability class, version boundary, CVSS vector, and references, but does not include detailed affected CPEs, exploit status, or operational prerequisites beyond secure-enclave RSA private-key use. Validate exposure through dependency and firmware analysis.
Mitigation direction
- Upgrade affected Mbed TLS deployments using Arm release guidance, including version 2.23.0 or later where applicable.
- For 2.16 LTS users, review Arm Mbed TLS v2.16.7 release guidance.
- Apply distribution security updates where Mbed TLS is supplied by the OS vendor.
- Inventory statically linked applications and firmware that may bundle vulnerable Mbed TLS.
- Rotate exposed RSA keys if investigation suggests enclave key disclosure may have occurred.
Validation and detection
- Identify all deployed Mbed TLS versions, including vendored source and static links.
- Check SBOMs, firmware manifests, and package inventories for Mbed TLS before 2.23.0.
- Confirm whether affected systems perform RSA private-key operations in secure enclave contexts.
- Verify OS packages include relevant Debian, Gentoo, or vendor security updates.
- Document compensating controls if immediate upgrade is not possible.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-203: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-36421 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ARMmbed/mbedtls/releases/tag/v2.16.7CVE reference
- https://github.com/ARMmbed/mbedtls/releases/tag/v2.23.0CVE reference
- https://github.com/ARMmbed/mbedtls/issues/3394CVE reference
- https://bugs.gentoo.org/730752CVE reference
- [debian-lts-announce] 20221225 [SECURITY] [DLA 3249-1] mbedtls security updateCVE reference · mailing-list
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Observable Discrepancy
Observable Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.