NULL Pointer Dereference Affecting libopenssl3 package, versions <3.0.1-150400.4.17.1


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.37% (73rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about NULL Pointer Dereference vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-SLES154-LIBOPENSSL3-3315091
  • published8 Feb 2023
  • disclosed7 Feb 2023

Introduced: 7 Feb 2023

CVE-2023-0401  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

Upgrade SLES:15.4 libopenssl3 to version 3.0.1-150400.4.17.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libopenssl3 package and not the libopenssl3 package as distributed by SLES. See How to fix? for SLES:15.4 relevant fixed versions and status.

A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash.

The unavailability of an algorithm can be caused by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider.

PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data.

CVSS Scores

version 3.1