An issue was discovered in wolfSSL before 5.5.0. When a TLS 1.3 client connects to a wolfSSL server and SSL_clear is called on its session, the server crashes with a segmentation fault. This occurs in the second session, which is created through TLS session resumption and reuses the initial struct WOLFSSL. If the server reuses the previous session structure (struct WOLFSSL) by calling wolfSSL_clear(WOLFSSL* ssl) on it, the next received Client Hello (that resumes the previous session) crashes the server. Note that this bug is only triggered when resuming sessions using TLS session resumption. Only servers that use wolfSSL_clear instead of the recommended SSL_free; SSL_new sequence are affected. Furthermore, wolfSSL_clear is part of wolfSSL's compatibility layer and is not enabled by default. It is not part of wolfSSL's native API.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - An issue was discovered in wolfSSL before 5.5.0. When a TLS 1.3 client connects to a wolfSSL server and
    SSL_clear is called on its session, the server crashes with a segmentation fault. This occurs in the
    second session, which is created through TLS session resumption and reuses the initial struct WOLFSSL. If
    the server reuses the previous session structure (struct WOLFSSL) by calling wolfSSL_clear(WOLFSSL* ssl)
    on it, the next received Client Hello (that resumes the previous session) crashes the server. Note that
    this bug is only triggered when resuming sessions using TLS session resumption. Only servers that use
    wolfSSL_clear instead of the recommended SSL_free; SSL_new sequence are affected. Furthermore,
    wolfSSL_clear is part of wolfSSL's compatibility layer and is not enabled by default. It is not part of
    wolfSSL's native API. (CVE-2022-38152)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - An issue was discovered in wolfSSL before 5.5.0. When a TLS 1.3 client connects to a wolfSSL server and     SSL_clear is called on its session, the server crashes with a segmentation fault. This occurs in the     second session, which is created through TLS session resumption and reuses the initial struct WOLFSSL. If     the server reuses the previous session structure (struct WOLFSSL) by calling wolfSSL_clear(WOLFSSL* ssl)     on it, the next received Client Hello (that resumes the previous session) crashes the server. Note that     this bug is only triggered when resuming sessions using TLS session resumption. Only servers that use     wolfSSL_clear instead of the recommended SSL_free; SSL_new sequence are affected. Furthermore,     wolfSSL_clear is part of wolfSSL's compatibility layer and is not enabled by default. It is not part of     wolfSSL's native API. (CVE-2022-38152)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
426263	Alpine: multiple wolfssl packages: security update to 5.5.0-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	high
426263	Alpine: multiple wolfssl packages: security update to 5.5.0-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	high
224871	Linux Distros Unpatched Vulnerability : CVE-2022-38152	Nessus	Misc.	high

Detections

Analytics

CVE-2022-38152

high

Tenable Plugins

high

high

high