CVE-2022-35409: An issue was discovered in Mbed TLS before 2.28.1 and 3.x before 3.2.0.
Noroxi assessment
Priority: Monitor (action score 37/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.3% (FIRST EPSS); higher than 83.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: mbedtls (Alpine:v3.16) 2.28.1-r0; mbedtls (Debian:10) 2.16.9-0~deb10u1; mbedtls (Debian:12) 2.28.1-1.
Low priority for now. Upgrade to mbedtls (Alpine:v3.16) 2.28.1-r0; mbedtls (Debian:10) 2.16.9-0~deb10u1; mbedtls (Debian:12) 2.28.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in Mbed TLS before 2.28.1 and 3.x before 3.2.0. In some configurations, an unauthenticated attacker can send an invalid ClientHello message to a DTLS server that causes a heap-based buffer over-read of up to 255 bytes. This can cause a server crash or possibly information disclosure based on error responses. Affected configurations have MBEDTLS_SSL_DTLS_CLIENT_PORT_REUSE enabled and MBEDTLS_SSL_IN_CONTENT_LEN less than a threshold that depends on the configuration: 258 bytes if using mbedtls_ssl_cookie_check, and possibly up to 571 bytes with a custom cookie check function.
- Published
- Jul 15, 2022
- Updated
- Jun 17, 2026
- EPSS
- 2.3% · 83th percentile
- CWE
- CWE-125
Report tools
Action score
37
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| arm | mbed tls | cpe:2.3:a:arm:mbed_tls |
| trustedfirmware | mbed tls | cpe:2.3:a:trustedfirmware:mbed_tls |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Check your server's TLS configuration
The Mbed TLS version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- arm mbed tlsbefore 2.28.1
- debian debian linux10.0
- trustedfirmware mbed tls3.0.0 and later · before 3.2.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.16 | mbedtls | before 2.28.1-r0 | 2.28.1-r0 |
| Debian:10 | mbedtls | before 2.16.9-0~deb10u1 | 2.16.9-0~deb10u1 |
| Debian:12 | mbedtls | before 2.28.1-1 | 2.28.1-1 |
| openSUSE:Leap 15.3 | mbedtls | before 2.16.9-bp153.2.8.1 | 2.16.9-bp153.2.8.1 |
| openSUSE:Tumbleweed | mbedtls-2 | before 2.28.1-1.1 | 2.28.1-1.1 |
| openSUSE:Tumbleweed | mbedtls-3 | before 3.6.6-1.1 | 3.6.6-1.1 |
| SUSE:Package Hub 15 SP3 | mbedtls | before 2.16.9-bp153.2.8.1 | 2.16.9-bp153.2.8.1 |
Same product
arm: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-47917Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation.40Plan
- CVE-2021-44732Mbed TLS before 3.0.1 has a double free in certain out-of-memory conditions, as demonstrated by an mbedtls_ssl_set_session() failure.40Plan
- CVE-2017-18187In ARM mbed TLS before 2.7.0, there is a bounds-check bypass through an integer overflow in PSK identity parsing in the ssl_parse_client_psk40Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-45451Dec 21, 2021 · In Mbed TLS before 3.1.0, psa_aead_generate_nonce allows policy bypass or oracle-based decryption when the output buffer is at memory locati30Monitor
- ← EarlierCVE-2021-43666Mar 24, 2022 · A Denial of Service vulnerability exists in mbed TLS 3.0.0 and earlier in the mbedtls_pkcs12_derivation function when an input password's le31Monitor
- Later →CVE-2022-46392Dec 15, 2022 · An issue was discovered in Mbed TLS before 2.28.2 and 3.x before 3.3.0.21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:mbedtls | 2.28.1-r0 · Alpine:v3.16 | Package registry (OSV) |
| debian:mbedtls | 2.28.1-1 · Debian:12 | Package registry (OSV) |
| opensuse:mbedtls | 2.16.9-bp153.2.8.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:mbedtls-2 | 2.28.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:mbedtls-3 | 3.6.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:mbedtls | 2.16.9-bp153.2.8.1 · SUSE:Package Hub 15 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.