The version of OpenSSL installed on the remote host is prior to 3.1.3. It is, therefore, affected by a vulnerability as referenced in the 3.1.3 advisory.

  - Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might     corrupt the internal state of applications on the Windows 64 platform when running on newer X86_64     processors supporting the AVX512-IFMA instructions. Impact summary: If in an application that uses the     OpenSSL library 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 does not save the contents of non-volatile XMM registers on     Windows 64 platform when calculating the MAC of data larger than 64 bytes. Before returning to the caller     all the XMM registers are set to zero rather than restoring their previous content. The vulnerable code is     used only on newer x86_64 processors supporting the AVX512-IFMA 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 given the     contents of the registers are just zeroized so the attacker cannot put arbitrary values inside, 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 and a malicious client can influence whether     this AEAD cipher is used by the server. This implies that 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. As a workaround the     AVX512-IFMA instructions support can be disabled at runtime by setting the environment variable     OPENSSL_ia32cap: OPENSSL_ia32cap=:~0x200000 The FIPS provider is not affected by this issue.
    (CVE-2023-4807)

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

Detections

Analytics

OpenSSL 3.1.0 < 3.1.3 Vulnerability

high Nessus Plugin ID 181290

Version 1.5

Version 1.4

Version 1.3

Version 1.2

Version 1.1

Version 1.0

Version 1.5 Oct 7, 2024, 1:27 PM Plugin categorization (adding new 'component' to component plugins) Plugin Feed: 202410071327
Version 1.4 Jun 7, 2024, 4:47 PM Detection (updated detection logic) Plugin Feed: 202406071647
Version 1.3 Nov 2, 2023, 4:31 AM IAVM reference Plugin Feed: 202311020431
Version 1.2 Sep 25, 2023, 2:20 PM CVSS metrics ("CVSSv2 score" changed from 4.3 to 6.8. "CVSSv3 score" set to 7.8. "CVSSv2 vector" changed from "CVSS2#AV:N/AC:M/Au:N/C:P/I:N/A:N" to "CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C". "CVSSv3 vector" set to "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H") CVSS temporal metrics ("CVSSv3 temporal vector" set to "CVSS:3.0/E:U/RL:O/RC:C") CVSSv3 score source (set to "CVE-2023-4807") Plugin Feed: 202309251420
Version 1.1 Sep 15, 2023, 12:17 PM IAVM reference STIG Severity (set to "I") Plugin Feed: 202309151217
Version 1.0 Sep 12, 2023, 10:01 PM New Plugin Feed: 202309122201