A use-after-free issue was addressed with improved memory management. This issue is fixed in macOS Monterey 12.6.8, iOS 15.7.8 and iPadOS 15.7.8, iOS 16.6 and iPadOS 16.6, tvOS 16.6, macOS Big Sur 11.7.9, macOS Ventura 13.5, watchOS 9.6. An app may be able to execute arbitrary code with kernel privileges.

According to its banner, the version of Apple TV on the remote device is prior to 16.6. It is therefore affected by multiple vulnerabilities as described in the HT213846

The version of Apple iOS running on the mobile device is prior to 16.6. It is, therefore, affected by multiple vulnerabilities.

The version of Apple iOS running on the mobile device is prior to 15.7.8. It is, therefore, affected by multiple vulnerabilities.

The remote host is running a version of macOS / Mac OS X that is 11.x prior to 11.7.9. It is, therefore, affected by multiple vulnerabilities:

  - A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH     server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the     fingerprint before it returns an error message containing the (now freed) hash. This flaw risks inserting     sensitive heap-based data into the error message that might be shown to users or otherwise get leaked and     revealed. (CVE-2023-28319)

  - A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different     backends for resolving host names, selected at build time. If it is built to use the synchronous resolver,     it allows name resolves to time-out slow operations using `alarm()` and `siglongjmp()`. When doing this,     libcurl used a global buffer that was not mutex protected and a multi-threaded application might therefore     crash or otherwise misbehave. (CVE-2023-28320)

  - An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of     wildcard patterns when listed as Subject Alternative Name in TLS server certificates. curl can be built     to use its own name matching function for TLS rather than one provided by a TLS library. This private     wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a     result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before     used for certificate checks. Puny coded names always start with `xn--` and should not be allowed to     pattern match, but the wildcard check in curl could still check for `x*`, which would match even though     the IDN name most likely contained nothing even resembling an `x`. (CVE-2023-28321)

  - An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might     erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the     `CURLOPT_POSTFIELDS` option has been set, if the same handle previously wasused to issue a `PUT` request     which used that callback. This flaw may surprise the application and cause it to misbehave and either send     off the wrong data or use memory after free or similar in the second transfer. The problem exists in the     logic for a reused handle when it is (expected to be) changed from a PUT to a POST. (CVE-2023-28322)

  - A vulnerability was found in openldap. This security flaw causes a null pointer dereference in     ber_memalloc_x() function. (CVE-2023-2953)

  - A use-after-free issue was addressed with improved memory management. (CVE-2023-32433, CVE-2023-35993)

  - This issue was addressed with improved state management. (CVE-2023-38606)

  - The issue was addressed with improved memory handling. (CVE-2023-32441)

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

The remote host is running a version of macOS / Mac OS X that is 13.x prior to 13.5. It is, therefore, affected by multiple vulnerabilities:

  - A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH     server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the     fingerprint before it returns an error message containing the (now freed) hash. This flaw risks inserting     sensitive heap-based data into the error message that might be shown to users or otherwise get leaked and     revealed. (CVE-2023-28319)

  - A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different     backends for resolving host names, selected at build time. If it is built to use the synchronous resolver,     it allows name resolves to time-out slow operations using `alarm()` and `siglongjmp()`. When doing this,     libcurl used a global buffer that was not mutex protected and a multi-threaded application might therefore     crash or otherwise misbehave. (CVE-2023-28320)

  - An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of     wildcard patterns when listed as Subject Alternative Name in TLS server certificates. curl can be built     to use its own name matching function for TLS rather than one provided by a TLS library. This private     wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a     result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before     used for certificate checks. Puny coded names always start with `xn--` and should not be allowed to     pattern match, but the wildcard check in curl could still check for `x*`, which would match even though     the IDN name most likely contained nothing even resembling an `x`. (CVE-2023-28321)

  - An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might     erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the     `CURLOPT_POSTFIELDS` option has been set, if the same handle previously wasused to issue a `PUT` request     which used that callback. This flaw may surprise the application and cause it to misbehave and either send     off the wrong data or use memory after free or similar in the second transfer. The problem exists in the     logic for a reused handle when it is (expected to be) changed from a PUT to a POST. (CVE-2023-28322)

  - A vulnerability was found in openldap. This security flaw causes a null pointer dereference in     ber_memalloc_x() function. (CVE-2023-2953)

  - This issue was addressed with improved data protection. (CVE-2023-35983)

  - A logic issue was addressed with improved restrictions. (CVE-2023-32416, CVE-2023-38259)

  - The issue was addressed with improved checks. (CVE-2023-32418, CVE-2023-36854, CVE-2023-37450,     CVE-2023-38133, CVE-2023-38572, CVE-2023-38594, CVE-2023-38595, CVE-2023-38597, CVE-2023-38600)

  - The issue was addressed with improved memory handling. (CVE-2023-32441, CVE-2023-32734, CVE-2023-38611)

  - A use-after-free issue was addressed with improved memory management. (CVE-2023-32381, CVE-2023-32433,     CVE-2023-35993)

  - This issue was addressed with improved state management. (CVE-2023-38606)

  - A path handling issue was addressed with improved validation. (CVE-2023-38565)

  - A logic issue was addressed with improved checks. (CVE-2023-38593)

  - A permissions issue was addressed with additional restrictions. (CVE-2023-38602)

  - An out-of-bounds read was addressed with improved input validation. (CVE-2023-32443)

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

The remote host is running a version of macOS / Mac OS X that is 12.x prior to 12.6.8. It is, therefore, affected by multiple vulnerabilities:

  - A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH     server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the     fingerprint before it returns an error message containing the (now freed) hash. This flaw risks inserting     sensitive heap-based data into the error message that might be shown to users or otherwise get leaked and     revealed. (CVE-2023-28319)

  - A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different     backends for resolving host names, selected at build time. If it is built to use the synchronous resolver,     it allows name resolves to time-out slow operations using `alarm()` and `siglongjmp()`. When doing this,     libcurl used a global buffer that was not mutex protected and a multi-threaded application might therefore     crash or otherwise misbehave. (CVE-2023-28320)

  - An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of     wildcard patterns when listed as Subject Alternative Name in TLS server certificates. curl can be built     to use its own name matching function for TLS rather than one provided by a TLS library. This private     wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a     result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before     used for certificate checks. Puny coded names always start with `xn--` and should not be allowed to     pattern match, but the wildcard check in curl could still check for `x*`, which would match even though     the IDN name most likely contained nothing even resembling an `x`. (CVE-2023-28321)

  - An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might     erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the     `CURLOPT_POSTFIELDS` option has been set, if the same handle previously wasused to issue a `PUT` request     which used that callback. This flaw may surprise the application and cause it to misbehave and either send     off the wrong data or use memory after free or similar in the second transfer. The problem exists in the     logic for a reused handle when it is (expected to be) changed from a PUT to a POST. (CVE-2023-28322)

  - A vulnerability was found in openldap. This security flaw causes a null pointer dereference in     ber_memalloc_x() function. (CVE-2023-2953)

  - This issue was addressed with improved data protection. (CVE-2023-35983)

  - A logic issue was addressed with improved restrictions. (CVE-2023-32416, CVE-2023-38259)

  - The issue was addressed with improved checks. (CVE-2023-32418, CVE-2023-36854, CVE-2023-38258,     CVE-2023-38421)

  - A use-after-free issue was addressed with improved memory management. (CVE-2023-32381, CVE-2023-32433,     CVE-2023-35993)

  - This issue was addressed with improved state management. (CVE-2023-38606)

  - The issue was addressed with improved memory handling. (CVE-2023-32441)

  - A path handling issue was addressed with improved validation. (CVE-2023-38565)

  - A logic issue was addressed with improved checks. (CVE-2023-38593)

  - A permissions issue was addressed with additional restrictions. (CVE-2023-38602)

  - An access issue was addressed with improved access restrictions. (CVE-2023-32442)

  - An out-of-bounds read was addressed with improved input validation. (CVE-2023-32443)

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

ID	Name	Product	Family	Severity
178942	Apple TV < 16.6 Multiple Vulnerabilities (HT213846)	Nessus	Misc.	high
178902	Apple iOS < 16.6 Multiple Vulnerabilities (HT213841)	Nessus	Mobile Devices	critical
178843	Apple iOS < 15.7.8 Multiple Vulnerabilities (HT213842)	Nessus	Mobile Devices	critical
178754	macOS 11.x < 11.7.9 Multiple Vulnerabilities (HT213845)	Nessus	MacOS X Local Security Checks	critical
178753	macOS 13.x < 13.5 Multiple Vulnerabilities (HT213843)	Nessus	MacOS X Local Security Checks	critical
178752	macOS 12.x < 12.6.8 Multiple Vulnerabilities (HT213844)	Nessus	MacOS X Local Security Checks	critical

Detections

Analytics

CVE-2023-35993

high

Tenable Plugins

high

critical

critical

critical

critical

critical