Source: wolfssl Version: 5.7.0-0.3 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/wolfSSL/wolfssl/pull/7604 X-Debbugs-Cc: car...@debian.org, Debian Security Team <t...@security.debian.org>
Hi, The following vulnerability was published for wolfssl. CVE-2024-5991[0]: | In function MatchDomainName(), input param str is treated as a NULL | terminated string despite being user provided and unchecked. | Specifically, the function X509_check_host() takes in a pointer and | length to check against, with no requirements that it be NULL | terminated. If a caller was attempting to do a name check on a non- | NULL terminated buffer, the code would read beyond the bounds of the | input array until it found a NULL terminator.This issue affects | wolfSSL: through 5.7.0. Note, I'm filling this with RC severity as all the recent uploads were done as NMU. Is wolfssl right now ok to be released for upcoming trixie or should we need to keep it out? If you fix the vulnerability please also make sure to include the raCVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-5991 https://www.cve.org/CVERecord?id=CVE-2024-5991 [1] https://github.com/wolfSSL/wolfssl/pull/7604 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
