dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-46393

CRITICAL · 9.8 CVSS v3.1 Published 2022-12-15
Fix available
A fix is available. Upgrade to 2.28.2 / 3.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in Mbed TLS before 2.28.2 and 3.x before 3.3.0. There is a potential heap-based buffer overflow and heap-based buffer over-read in DTLS if MBEDTLS_SSL_DTLS_CONNECTION_ID is enabled and MBEDTLS_SSL_CID_IN_LEN_MAX > 2 * MBEDTLS_SSL_CID_OUT_LEN_MAX.

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 confidence

Heap-based buffer overflow and over-read vulnerability in Mbed TLS DTLS implementation when MBEDTLS_SSL_DTLS_CONNECTION_ID is enabled and the maximum input CID length exceeds twice the maximum output CID length. This memory corruption flaw can be triggered during DTLS handshake processing, potentially allowing remote code execution or sensitive memory disclosure.

MitigationUpgrade Mbed TLS to version 2.28.2 or 3.3.0, or disable DTLS Connection IDs if not required. Ensure MBEDTLS_SSL_CID_IN_LEN_MAX is not greater than 2*MBEDTLS_SSL_CID_OUT_LEN_MAX.

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
Affected:= 36= 37
Mbed TlsApplication
Affected:< 2.28.2
Mbed TlsApplication
Affected:>= 3.0.0, < 3.3.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Mbed TLS version
    Check the installed Mbed TLS library version. On Linux systems, this can be done via package manager (e.g., 'rpm -q mbedtls' on Fedora) or by checking the library file version. For embedded builds, inspect the build configuration header files for the version definition (e.g., MBEDTLS_VERSION_NUMBER).
    Affected if The version is less than 2.28.2 for the 2.x branch, or between 3.0.0 and 3.2.x for the 3.x branch (versions 3.0.0 through 3.2.x are affected).
  2. Confirm DTLS Connection ID feature is enabled
    Inspect the Mbed TLS build configuration (mbedtls_config.h or the build defines) for the macro MBEDTLS_SSL_DTLS_CONNECTION_ID. Search for '#define MBEDTLS_SSL_DTLS_CONNECTION_ID' or check compile-time configuration options.
    Affected if The macro MBEDTLS_SSL_DTLS_CONNECTION_ID is defined/enabled, meaning DTLS Connection IDs are compiled into the library.
  3. Check CID length configuration limits
    Inspect the build configuration for MBEDTLS_SSL_CID_IN_LEN_MAX and MBEDTLS_SSL_CID_OUT_LEN_MAX macros. These define the maximum input and output CID lengths respectively. Look in mbedtls_config.h or the relevant configuration header.
    Affected if The value of MBEDTLS_SSL_CID_IN_LEN_MAX is greater than two times MBEDTLS_SSL_CID_OUT_LEN_MAX (i.e., MBEDTLS_SSL_CID_IN_LEN_MAX > 2 * MBEDTLS_SSL_CID_OUT_LEN_MAX).

You are affected if you run a vulnerable Mbed TLS version (<2.28.2 or 3.0.0-3.2.x), have DTLS Connection IDs enabled, and have configured the input CID length limit to exceed twice the output CID length limit.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.28.2 / 3.3.0 or later
Fixed in 2.28.23.3.0
Interim mitigation

Upgrade Mbed TLS to version 2.28.2 or 3.3.0, or disable DTLS Connection IDs if not required. Ensure MBEDTLS_SSL_CID_IN_LEN_MAX is not greater than 2*MBEDTLS_SSL_CID_OUT_LEN_MAX.

Recommended fix High confidence

Mbed TLS 2.28.2 (for 2.x branch) or Mbed TLS 3.3.0 (for 3.x branch)

  1. Identify whether your project uses Mbed TLS 2.x or 3.x branch
  2. If using Mbed TLS 2.x: upgrade to version 2.28.2
  3. If using Mbed TLS 3.x: upgrade to version 3.3.0
  4. After upgrade, verify the version using mbedtls_version_get_number() or equivalent
  5. Rebuild and redeploy your application with the updated Mbed TLS library
  6. Test DTLS functionality to ensure proper operation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-46393 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-46393 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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