CVE-2022-34293
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 · uneditedwolfSSL before 5.4.0 allows remote attackers to cause a denial of service via DTLS because a check for return-routability can be skipped.
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 confidencewolfSSL before version 5.4.0 contains a vulnerability in its DTLS implementation where a return-routability check can be skipped. This allows remote attackers to potentially send spoofed DTLS packets that bypass this security check, leading to resource consumption and denial of service. The vulnerability stems from insufficient validation of the source address in DTLS handshake processing.
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< 5.4.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify wolfSSL installation and versionRun 'wolfssl version' or check package manager for installed wolfssl/wolfssl package version. If built from source, check the version.h file or the output of 'grep WOLFSSL_VERSION ./wolfssl/version.h'Affected if The installed version is below 5.4.0 (e.g., 5.3.0, 5.2.0, etc.)
-
Confirm DTLS protocol is in useInspect application configuration files, runtime settings, or network traffic to determine if DTLS (Datagram Transport Layer Security) is enabled. Check for DTLS-related configuration options in the application using wolfSSL (such as SSL_DTLS, SSL_OP_COOKIE_EXCHANGE, or similar DTLS-specific flags)Affected if DTLS is enabled and the wolfSSL version is below 5.4.0
-
Verify exposed DTLS servicesScan listening ports for DTLS services (typically UDP ports 443, 4433, 8443, or custom DTLS ports). Use 'netstat -anu' or 'ss -anu' to list UDP listeners, and verify if the service using those ports relies on wolfSSLAffected if DTLS services are exposed and wolfSSL version is below 5.4.0
You are affected if your environment runs any version of wolfSSL prior to 5.4.0 with DTLS functionality enabled and exposed.
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 · scoped5.4.0
Upgrade wolfSSL to version 5.4.0 or later to obtain the patched version that properly enforces return-routability checks in DTLS connections. If immediate upgrading is not feasible, consider restricting DTLS exposure to trusted networks or implementing additional network-level controls.
wolfSSL 5.4.0
- Check current wolfSSL version using 'wolfssl -V' or checking library version in your application
- Download wolfSSL 5.4.0 or later from the official wolfSSL repository (github.com/wolfSSL/wolfssl)
- Compile and install the new version following standard wolfSSL build procedures
- Restart any services or applications using wolfSSL to load the updated library
- Verify the installed version is 5.4.0 or later using 'wolfssl -V'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34293 — 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-34293 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