# CVE-2022-34293: Denial of service in n/a

> Remote attackers can cause a denial of service in wolfSSL by bypassing DTLS return-routability checks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-34293, GHSA-w837-4755-g9cj, JLSEC-2026-671, UBUNTU-CVE-2022-34293

## What is CVE-2022-34293?

CVE-2022-34293 is a high-severity denial of service vulnerability in Wolfssl Wolfssl, published on 8 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

wolfSSL before 5.4.0 allows remote attackers to cause a denial of service via DTLS because a check for return-routability can be skipped.

## Which versions are affected by CVE-2022-34293?

It affects 1 product.


Products: Wolfssl Wolfssl.

## How do I fix CVE-2022-34293?

Upgrade to a fixed version.

## Is CVE-2022-34293 being exploited?

There is no known exploitation of CVE-2022-34293 in the wild and no public exploit code.

## Other vulnerabilities in Wolfssl Wolfssl

- [CVE-2024-5991](https://insights.sbomify.com/CVE-2024-5991/): Buffer overread in domain name matching (critical 10.0)
- [CVE-2021-37155](https://insights.sbomify.com/CVE-2021-37155/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-36177](https://insights.sbomify.com/CVE-2020-36177/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2896](https://insights.sbomify.com/CVE-2014-2896/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2897](https://insights.sbomify.com/CVE-2014-2897/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34293 and fix it if it is affected.

What it is: CVE-2022-34293 is a high-severity denial of service vulnerability in Wolfssl Wolfssl, published on 8 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34293 in the wild and no public exploit code.

Affected product: Wolfssl Wolfssl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-34293/ (Markdown: https://insights.sbomify.com/CVE-2022-34293/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-34293
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-34293
- OSV: https://osv.dev/vulnerability/CVE-2022-34293

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-34293/
Summaries are generated and may contain mistakes; the official description above is the record.