CVE-2023-6936: Heap-buffer over-read with WOLFSSL_CALLBACKS
First published: Tue Feb 20 2024(Updated: )
In wolfSSL prior to 5.6.6, if callback functions are enabled (via the WOLFSSL_CALLBACKS flag), then a malicious TLS client or network attacker can trigger a buffer over-read on the heap of 5 bytes (WOLFSSL_CALLBACKS is only intended for debugging).
Credit: facts@wolfssl.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| wolfSSL | <5.6.6 |
Remedy
The fix for this issue is located in the following GitHub Pull Request: https://github.com/wolfSSL/wolfssl/pull/6949/ https://github.com/wolfSSL/wolfssl/pull/6949/
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2023-6936?
CVE-2023-6936 is classified as a medium severity vulnerability due to the potential buffer over-read it poses.
How do I fix CVE-2023-6936?
To fix CVE-2023-6936, upgrade to wolfSSL version 5.6.6 or later where this issue has been resolved.
What impact does CVE-2023-6936 have on my system?
CVE-2023-6936 can allow a malicious TLS client or network attacker to trigger a buffer over-read, potentially leading to information leakage.
Which versions of wolfSSL are affected by CVE-2023-6936?
CVE-2023-6936 affects wolfSSL versions prior to 5.6.6.
Is enabling WOLFSSL_CALLBACKS safe in light of CVE-2023-6936?
Enabling WOLFSSL_CALLBACKS is not safe for production environments due to the vulnerability introduced in CVE-2023-6936.
- agent/remedy
- agent/title
- agent/references
- agent/type
- agent/first-publish-date
- agent/description
- agent/severity
- agent/author
- agent/event
- collector/nvd-api
- source/NVD
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/wolfssl
- canonical/wolfssl