It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2022-2022-157 advisory.

  - 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 the malicious certificate or for the application to continue certificate verification despite     failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to     overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash     (causing a denial of service) or potentially remote code execution. Many platforms implement stack     overflow protections which would mitigate against the risk of remote code execution. The risk may be     further mitigated based on stack layout for any given platform/compiler. Pre-announcements of     CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors     described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new     version as soon as possible. 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. Fixed in OpenSSL 3.0.7 (Affected 3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6). (CVE-2022-3602)

  - 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. Fixed in OpenSSL 3.0.7 (Affected     3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6). (CVE-2022-3786)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Detections

Analytics

Amazon Linux 2022 : (ALAS2022-2022-157)

high Nessus Plugin ID 166782

Version 1.8

Version 1.7

Version 1.6

Version 1.5

Version 1.4

Version 1.3

Version 1.2

Version 1.8 Dec 15, 2022, 4:16 PM IAVM reference Plugin Feed: 202212151616
Version 1.7 Dec 5, 2022, 10:02 PM Reference Plugin Feed: 202212052202
Version 1.6 Nov 28, 2022, 4:23 PM CVSS metrics ("CVSSv2 score" changed from "7.5" to "7.8") CVSS metrics ("CVSSv2 vector" changed from "CVSS2#AV:N/AC:L/Au:N/C:P/I:P/A:P" to "CVSS2#AV:N/AC:L/Au:N/C:N/I:N/A:C") CVSSv2 score source (changed from "CVE-2022-3602" to "CVE-2022-3786") Plugin Feed: 202211281623
Version 1.5 Nov 7, 2022, 3:54 PM CVSS metrics CVSSv3 score source (Changed from None to CVE-2022-3786) Plugin Feed: 202211071554
Version 1.4 Nov 4, 2022, 11:48 AM IAVM reference STIG Severity Plugin Feed: 202211041148
Version 1.3 Nov 3, 2022, 4:28 PM CVSS metrics CVSSv3 score source (Changed from None to CVE-2022-3602) Plugin Feed: 202211031628
Version 1.2 Nov 2, 2022, 11:45 AM New Plugin Feed: 202211021145