Security readout for executives and security teams
Plain-English summary
This vulnerability can let a highly capable attacker recover an RSA private key from vulnerable Mbed TLS use. The scenario is specialized: the attacker needs very precise memory-access observations, commonly an untrusted operating system attacking a secure enclave. Business urgency is moderate unless your products use Mbed TLS for RSA private-key operations in enclave-like or hostile-host environments.
Executive priority
Treat as a targeted confidentiality risk, not a broad internet emergency. Prioritize systems where private keys protect customer data, firmware trust, device identity, or enclave workloads. Patch through normal security maintenance unless your environment matches the hostile-host memory-observation scenario.
Technical view
Mbed TLS before 2.28.2 and 3.x before 3.3.0 leaks information through observable memory-access behavior during RSA private-key exponentiation when MBEDTLS_MPI_WINDOW_SIZE is 3 or smaller. The CVE maps to CWE-203 and is scored CVSS 3.1 5.3, with high confidentiality impact but high attack complexity.
Likely exposure
Exposure is most likely in embedded, appliance, application, or enclave workloads using affected Mbed TLS versions for RSA private-key operations. Risk is higher when an attacker can observe memory access patterns from a privileged or host position. The provided affected-product metadata is incomplete.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The described attack requires precise memory-access information and a victim private-key operation. Sources specifically describe a secure-enclave style threat model involving an untrusted operating system.
Researcher notes
This is a side-channel issue, not a memory-corruption bug. The strongest exposure signal is the combination of affected Mbed TLS versions, RSA private-key use, small MPI window size, and an attacker able to monitor memory accesses. The bundle does not provide exploit activity or complete downstream product impact.
Mitigation direction
- Upgrade Mbed TLS to 2.28.2, 3.3.0, or later supported versions.
- Apply downstream OS or vendor package updates where Mbed TLS is bundled.
- Identify products and services performing RSA private-key operations with Mbed TLS.
- Review MBEDTLS_MPI_WINDOW_SIZE settings in affected builds.
- If immediate patching is impossible, check vendor guidance for supported compensating controls.
Validation and detection
- Inventory all direct and bundled Mbed TLS versions.
- Confirm whether RSA private-key operations use affected library builds.
- Check build configuration for MBEDTLS_MPI_WINDOW_SIZE of 3 or smaller.
- Verify patched package versions from vendor or distribution advisories.
- Prioritize enclave, TEE, embedded, and hostile-host deployments for review.
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-2022-46392 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:H/PR:N/UI:R/S:U/C:H/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:H/PR:N/UI:R/S:U/C:H/I:N/A:N1.63.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Mbed-TLS/mbedtls/releases/tag/v3.3.0CVE reference
- https://github.com/Mbed-TLS/mbedtls/releases/tag/v2.28.2CVE reference
- FEDORA-2023-7456a62f60CVE reference · vendor-advisory
- FEDORA-2023-3c4a525dccCVE reference · vendor-advisory
- https://lists.debian.org/debian-lts-announce/2025/06/msg00034.htmlCVE reference
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.