Buffer Overflow Affecting libopenssl3 package, versions <3.0.1-150400.4.11.1


Severity

Recommended
high

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.13% (48th 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 IDSNYK-SLES154-LIBOPENSSL3-3092966
  • published2 Nov 2022
  • disclosed1 Nov 2022

Introduced: 1 Nov 2022

CVE-2022-3786  (opens in a new tab)
CWE-120  (opens in a new tab)

How to fix?

Upgrade SLES:15.4 libopenssl3 to version 3.0.1-150400.4.11.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 buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.' character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

References

CVSS Scores

version 3.1