The version of OpenSSL installed on the remote host is prior to 3.2.1. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.2.1 advisory.

  - Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a     potential Denial of Service attack Impact summary: Applications loading files in the PKCS12 format from     untrusted sources might terminate abruptly. A file in PKCS12 format can contain certificates and keys and     may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL     does not correctly check for this case. This can lead to a NULL pointer dereference that results in     OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs     then that application will be vulnerable to this issue. OpenSSL APIs that are vulnerable to this are:
    PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and     PKCS12_newpass(). We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function     is related to writing data we do not consider it security significant. The FIPS modules in 3.2, 3.1 and     3.0 are not affected by this issue. (CVE-2024-0727)

  - Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might     corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides     vector instructions. Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is     used, the application state might be corrupted with various application dependent consequences. The     POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the     contents of vector registers in a different order than they are saved. Thus the contents of some of these     vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer     PowerPC processors supporting the PowerISA 2.07 instructions. The consequences of this kind of internal     application state corruption can be various - from no consequences, if the calling application does not     depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker     could get complete control of the application process. However unless the compiler uses the vector     registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some     application dependent calculations or a crash leading to a denial of service. The POLY1305 MAC algorithm     is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated     data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If     this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used.
    This implies that TLS server applications using OpenSSL can be potentially impacted. However we are     currently not aware of any concrete application that would be affected by this issue therefore we consider     this a Low severity security issue. (CVE-2023-6129)

  - Issue summary: Checking excessively long invalid RSA public keys may take a long time. Impact summary:
    Applications that use the function EVP_PKEY_public_check() to check RSA public keys may experience long     delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a     Denial of Service. When function EVP_PKEY_public_check() is called on RSA public keys, a computation is     done to confirm that the RSA modulus, n, is composite. For valid RSA keys, n is a product of two or more     large primes and this computation completes quickly. However, if n is an overly large prime, then this     computation would take a long time. An application that calls EVP_PKEY_public_check() and supplies an RSA     key obtained from an untrusted source could be vulnerable to a Denial of Service attack. The function     EVP_PKEY_public_check() is not called from other OpenSSL functions however it is called from the OpenSSL     pkey command line application. For that reason that application is also vulnerable if used with the
    -pubin' and -check' options on untrusted data. The OpenSSL SSL/TLS implementation is not affected by     this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue. Found by OSS-Fuzz. Fix     developed by Tomas Mraz. Fixed in OpenSSL 3.1.5 (Affected since 3.1.0). (CVE-2023-6237)

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

Detections

Analytics

OpenSSL 3.2.0 < 3.2.1 Multiple Vulnerabilities

medium Nessus Plugin ID 187783

Version 1.8

Version 1.7

Version 1.6

Version 1.5

Version 1.5

Version 1.4

Version 1.3

Version 1.2

Version 1.2

Version 1.1

Version 1.0

Version 1.0

Version 1.8 Apr 11, 2024, 4:12 PM IAVM reference Plugin Feed: 202404111612
Version 1.7 Mar 8, 2024, 4:03 PM STIG Severity (set to "I") IAVM reference Plugin Feed: 202403081603
Version 1.6 Jan 31, 2024, 7:13 PM Plugin metadata Plugin Feed: 202401311913
Version 1.5 Jan 25, 2024, 10:12 PM CVE (set "CVE" coverage to "CVE-2023-6129,CVE-2023-6237,CVE-2024-0727") Plugin metadata Plugin Feed: 202401252212
Version 1.5 Jan 31, 2024, 5:24 PM Plugin metadata Plugin Feed: 202401311724
Version 1.4 Jan 24, 2024, 7:17 PM CVSS metrics ("CVSSv2 score" set to 6.1. "CVSSv2 vector" set to "CVSS2#AV:N/AC:H/Au:N/C:N/I:P/A:C". "CVSSv3 score" set to 6.5. "CVSSv3 vector" set to "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H") Plugin Feed: 202401241917
Version 1.3 Jan 16, 2024, 3:43 PM CVSSv3 score source (changed from "CVE-2023-6237" to none) Plugin Feed: 202401161543
Version 1.2 Jan 15, 2024, 4:36 PM CVE (set "CVE" coverage to "CVE-2023-6129,CVE-2023-6237") CVSSv3 score source (set to "CVE-2023-6237") Plugin metadata Plugin Feed: 202401151636
Version 1.2 Jan 16, 2024, 1:47 PM CVSSv3 score source (changed from "CVE-2023-6237" to none) Plugin Feed: 202401161347
Version 1.1 Jan 10, 2024, 5:28 PM Plugin metadata Plugin Feed: 202401101728
Version 1.0 Jan 10, 2024, 8:45 AM New Plugin Feed: 202401100845
Version 1.0 Jan 10, 2024, 3:27 PM Plugin metadata Plugin Feed: 202401101527