FedoraOperating system · Fedoraproject
CVE-2022-46392
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 · uneditedAn issue was discovered in Mbed TLS before 2.28.2 and 3.x before 3.3.0. An adversary with access to precise enough information about memory accesses (typically, an untrusted operating system attacking a secure enclave) can recover an RSA private key after observing the victim performing a single private-key operation, if the window size (MBEDTLS_MPI_WINDOW_SIZE) used for the exponentiation is 3 or smaller.
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 · high confidenceThis is a side-channel attack vulnerability in Mbed TLS RSA implementation. An attacker with precise memory access information (typically an untrusted OS attacking a secure enclave) can recover an RSA private key after observing just one private-key operation, when the MBEDTLS_MPI_WINDOW_SIZE is set to 3 or smaller. The smaller window size creates predictable memory access patterns that leak key material.
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
FedoraOperating system
= 36= 37< 2.28.2>= 3.0.0, < 3.3.0CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Identify Mbed TLS installation and versionLocate Mbed TLS libraries (libmbedcrypto, libmbedtls, libmbedx509) and query their version using package manager (dnf/rpm on Fedora) or by inspecting library files. Check /usr/lib/ and /usr/include/ for Mbed TLS files.Affected if Installed version is Arm Mbed TLS < 2.28.2, or >= 3.0.0 and < 3.3.0, or running on Fedora 36/37 with unpatched Mbed TLS packages
-
Locate Mbed TLS configuration headerSearch for mbedtls_config.h or config.h in the project include directories, typically at include/mbedtls/mbedtls_config.h or in the build configuration directory.Affected if The configuration file exists and is being used by the compiled library
-
Check MBEDTLS_MPI_WINDOW_SIZE valueOpen the mbedtls_config.h file and search for MBEDTLS_MPI_WINDOW_SIZE definition. Look for lines like '#define MBEDTLS_MPI_WINDOW_SIZE 3' or similar.Affected if MBEDTLS_MPI_WINDOW_SIZE is defined to a value of 3 or less, or is not defined (which defaults to a vulnerable value)
-
Verify RSA is enabledConfirm that RSA functionality is compiled into the library by checking for MBEDTLS_RSA_C defined in the config file, and that RSA operations are being performed.Affected if RSA is enabled and private-key operations (decryption or signing) are performed using RSA
The environment is affected if Mbed TLS version is vulnerable AND MBEDTLS_MPI_WINDOW_SIZE is set to 3 or smaller AND RSA private-key operations are being performed.
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.
dbcve · scoped2.28.23.3.0
Upgrade Mbed TLS to version 2.28.2 or 3.3.0 or later. If immediate upgrading is not feasible, increase MBEDTLS_MPI_WINDOW_SIZE to a value greater than 3 (typically 4 or higher) in the configuration.
Mbed TLS 2.28.2 (for 2.x users) or Mbed TLS 3.3.0 (for 3.x users)
- 1. Identify the currently installed Mbed TLS version by checking your project's dependencies or system packages
- 2. If using Mbed TLS 2.x line, upgrade to version 2.28.2 or later
- 3. If using Mbed TLS 3.x line, upgrade to version 3.3.0 or later
- 4. For Fedora systems: run 'dnf update mbedtls' to apply available security updates for versions 36 and 37
- 5. Rebuild any applications that link against Mbed TLS to ensure they use the updated library
- 6. Verify the upgrade was successful by checking the new version matches or exceeds the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46392 — 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-2022-46392 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