The version of AOS installed on the remote host is prior to 6.7.1.5. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AOS-6.7.1.5 advisory.

  - Incomplete Cleanup vulnerability in Apache Tomcat. The internal fork of Commons FileUpload packaged with     Apache Tomcat 9.0.70 through 9.0.80 and 8.5.85 through 8.5.93 included an unreleased, in progress     refactoring that exposed a potential denial of service on Windows if a web application opened a stream for     an uploaded file but failed to close the stream. The file would never be deleted from disk creating the     possibility of an eventual denial of service due to the disk being full. Users are recommended to upgrade     to version 9.0.81 onwards or 8.5.94 onwards, which fixes the issue. (CVE-2023-42794)

  - Incomplete Cleanup vulnerability in Apache Tomcat.When recycling various internal objects in Apache Tomcat     from 11.0.0-M1 through 11.0.0-M11, from 10.1.0-M1 through 10.1.13, from 9.0.0-M1 through 9.0.80 and from     8.5.0 through 8.5.93, an error could cause Tomcat to skip some parts of the recycling process leading to     information leaking from the current request/response to the next. Users are recommended to upgrade to     version 11.0.0-M12 onwards, 10.1.14 onwards, 9.0.81 onwards or 8.5.94 onwards, which fixes the issue.
    (CVE-2023-42795)

  - The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation     can reset many streams quickly, as exploited in the wild in August through October 2023. (CVE-2023-44487)

  - Improper Input Validation vulnerability in Apache Tomcat.Tomcat from 11.0.0-M1 through 11.0.0-M11, from     10.1.0-M1 through 10.1.13, from 9.0.0-M1 through 9.0.81 and from 8.5.0 through 8.5.93 did not correctly     parse HTTP trailer headers. A specially crafted, invalid trailer header could cause Tomcat to treat a     single request as multiple requests leading to the possibility of request smuggling when behind a reverse     proxy. Users are recommended to upgrade to version 11.0.0-M12 onwards, 10.1.14 onwards, 9.0.81 onwards or     8.5.94 onwards, which fix the issue. (CVE-2023-45648)

  - While parsing an IPAddressFamily extension in an X.509 certificate, it is possible to do a one-byte     overread. This would result in an incorrect text display of the certificate. This bug has been present     since 2006 and is present in all versions of OpenSSL before 1.0.2m and 1.1.0g. (CVE-2017-3735)

  - There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL before 1.0.2m and     1.1.0 before 1.1.0g. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as     a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH     are considered just feasible (although very difficult) because most of the work necessary to deduce     information about a private key may be performed offline. The amount of resources required for such an     attack would be very significant and likely only accessible to a limited number of attackers. An attacker     would additionally need online access to an unpatched system using the target private key in a scenario     with persistent DH parameters and a private key that is shared between multiple clients. This only affects     processors that support the BMI1, BMI2 and ADX extensions like Intel Broadwell (5th generation) and later     or AMD Ryzen. (CVE-2017-3736)

  - The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An     attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a     (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected     1.0.2-1.0.2p). (CVE-2018-0734)

  - Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to     timing attacks via a side-channel timing attack on 'port contention'. (CVE-2018-5407)

  - If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a     close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if     a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an     invalid MAC. If the application then behaves differently based on that in a way that is detectable to the     remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order for this     to be exploitable non-stitched ciphersuites must be in use. Stitched ciphersuites are optimised     implementations of certain commonly used ciphersuites. Also the application must call SSL_shutdown() twice     even if a protocol error has occurred (applications should not do this but some do anyway). Fixed in     OpenSSL 1.0.2r (Affected 1.0.2-1.0.2q). (CVE-2019-1559)

  - OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an error state mechanism. The intent was that if     a fatal error occurred during a handshake then OpenSSL would move into the error state and would     immediately fail if you attempted to continue the handshake. This works as designed for the explicit     handshake functions (SSL_do_handshake(), SSL_accept() and SSL_connect()), however due to a bug it does not     work correctly if SSL_read() or SSL_write() is called directly. In that scenario, if the handshake fails     then a fatal error will be returned in the initial function call. If SSL_read()/SSL_write() is     subsequently called by the application for the same SSL object then it will succeed and the data is passed     without being decrypted/encrypted directly from the SSL/TLS record layer. In order to exploit this issue     an application bug would have to be present that resulted in a call to SSL_read()/SSL_write() being issued     after having already received a fatal error. OpenSSL version 1.0.2b-1.0.2m are affected. Fixed in OpenSSL     1.0.2n. OpenSSL 1.1.0 is not affected. (CVE-2017-3737)

  - There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with     1024-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a     result of this defect would be very difficult to perform and are not believed likely. Attacks against     DH1024 are considered just feasible, because most of the work necessary to deduce information about a     private key may be performed offline. The amount of resources required for such an attack would be     significant. However, for an attack on TLS to be meaningful, the server would have to share the DH1024     private key among multiple clients, which is no longer an option since CVE-2016-0701. This only affects     processors that support the AVX2 but not ADX extensions like Intel Haswell (4th generation). Note: The     impact from this issue is similar to CVE-2017-3736, CVE-2017-3732 and CVE-2015-3193. OpenSSL version     1.0.2-1.0.2m and 1.1.0-1.1.0g are affected. Fixed in OpenSSL 1.0.2n. Due to the low severity of this issue     we are not issuing a new release of OpenSSL 1.1.0 at this time. The fix will be included in OpenSSL 1.1.0h     when it becomes available. The fix is also available in commit e502cc86d in the OpenSSL git repository.
    (CVE-2017-3738)

  - Constructed ASN.1 types with a recursive definition (such as can be found in PKCS7) could eventually     exceed the stack given malicious input with excessive recursion. This could result in a Denial Of Service     attack. There are no such structures used within SSL/TLS that come from untrusted sources so this is     considered safe. Fixed in OpenSSL 1.1.0h (Affected 1.1.0-1.1.0g). Fixed in OpenSSL 1.0.2o (Affected     1.0.2b-1.0.2n). (CVE-2018-0739)

  - During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very     large prime value to the client. This will cause the client to spend an unreasonably long period of time     generating a key for this prime resulting in a hang until the client has finished. This could be exploited     in a Denial Of Service attack. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL     1.0.2p-dev (Affected 1.0.2-1.0.2o). (CVE-2018-0732)

  - The OpenSSL RSA Key generation algorithm has been shown to be vulnerable to a cache timing side channel     attack. An attacker with sufficient access to mount cache timing attacks during the RSA key generation     process could recover the private key. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in     OpenSSL 1.0.2p-dev (Affected 1.0.2b-1.0.2o). (CVE-2018-0737)

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

Detections

Analytics

Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-6.7.1.5)

medium Nessus Plugin ID 189370

Version 1.8

Version 1.7

Version 1.6

Version 1.6

Version 1.5

Version 1.4

Version 1.3

Version 1.2

Version 1.2

Version 1.1

Version 1.1

Version 1.0

Version 1.8 Mar 6, 2024, 8:53 AM Plugin metadata Plugin Feed: 202403060853
Version 1.7 Mar 5, 2024, 7:01 AM Plugin metadata Plugin Feed: 202403050701
Version 1.6 Feb 14, 2024, 5:20 PM Plugin metadata Plugin Feed: 202402141720
Version 1.6 Mar 5, 2024, 4:36 AM Plugin metadata Plugin Feed: 202403050436
Version 1.5 Feb 9, 2024, 11:26 PM CEA reference Plugin Feed: 202402092326
Version 1.4 Feb 2, 2024, 12:15 PM Plugin metadata Plugin Feed: 202402021215
Version 1.3 Feb 2, 2024, 1:41 AM Plugin metadata Plugin Feed: 202402020141
Version 1.2 Feb 1, 2024, 2:31 PM Plugin metadata Plugin Feed: 202402011431
Version 1.2 Feb 1, 2024, 11:53 PM Plugin metadata Plugin Feed: 202402012353
Version 1.1 Jan 24, 2024, 9:29 PM CEA reference Plugin Feed: 202401242129
Version 1.1 Feb 1, 2024, 12:41 PM Plugin metadata Plugin Feed: 202402011241
Version 1.0 Jan 23, 2024, 11:06 PM New Plugin Feed: 202401232306