According to the versions of the libxml2 packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the     XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to     access an array at a negative 2GB offset, typically leading to a segmentation fault. (CVE-2022-40303)

  - An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a     hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be     provoked. (CVE-2022-40304)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Rocky Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2023:0338 advisory.

  - An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the     XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to     access an array at a negative 2GB offset, typically leading to a segmentation fault. (CVE-2022-40303)

  - An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a     hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be     provoked. (CVE-2022-40304)

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

The remote CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CESA-2023:0173 advisory.

  - An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the     XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to     access an array at a negative 2GB offset, typically leading to a segmentation fault. (CVE-2022-40303)

  - An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a     hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be     provoked. (CVE-2022-40304)

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

The remote Redhat Enterprise Linux 6 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - libxml2: Use after free via namespace node in XPointer ranges (CVE-2016-4658)

  - libxml2: Missing validation for external entities in xmlParsePEReference (CVE-2017-7375)

  - Possible cross-site scripting vulnerability in libxml after commit 960f0e2. (CVE-2016-3709)

  - The xmlBufAttrSerializeTxtContent function in xmlsave.c in libxml2 allows context-dependent attackers to     cause a denial of service (out-of-bounds read and application crash) via a non-UTF-8 attribute value,     related to serialization. NOTE: this vulnerability may be a duplicate of CVE-2016-3627. (CVE-2016-4483)

  - Use-after-free vulnerability in libxml2 through 2.9.4, as used in Google Chrome before 52.0.2743.82,     allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors     related to the XPointer range-to function. (CVE-2016-5131)

  - libxml2 2.9.4 and earlier, as used in XMLSec 1.2.23 and earlier and other products, does not offer a flag     directly indicating that the current document may be read but other files may not be opened, which makes     it easier for remote attackers to conduct XML External Entity (XXE) attacks via a crafted document.
    (CVE-2016-9318)

  - A remote code execution vulnerability in libxml2 could enable an attacker using a specially crafted file     to execute arbitrary code within the context of an unprivileged process. This issue is rated as High due     to the possibility of remote code execution in an application that uses this library. Product: Android.
    Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2. Android ID: A-37104170. (CVE-2017-0663)

  - Use after free in libxml2 before 2.9.5, as used in Google Chrome prior to 63.0.3239.84 and other products,     allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (CVE-2017-15412)

  - parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the     xmlParserHandlePEReference function in the case of a '%' character in a DTD name. (CVE-2017-16931)

  - parser.c in libxml2 before 2.9.5 does not prevent infinite recursion in parameter entities.
    (CVE-2017-16932)

  - libxml2 2.9.4, when used in recover mode, allows remote attackers to cause a denial of service (NULL     pointer dereference) via a crafted XML document. NOTE: The maintainer states I would disagree of a CVE     with the Recover parsing option which should only be used for manual recovery at least for XML parser.
    (CVE-2017-5969)

  - The htmlParseTryOrFinish function in HTMLparser.c in libxml2 2.9.4 allows attackers to cause a denial of     service (buffer over-read) or information disclosure. (CVE-2017-8872)

  - A buffer overflow was discovered in libxml2 20904-GITv2.9.4-16-g0741801. The function     xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a     char buffer 'buf' of size 'size'. The variable len is assigned strlen(buf). If the content->type is     XML_ELEMENT_CONTENT_ELEMENT, then (i) the content->prefix is appended to buf (if it actually fits)     whereupon (ii) content->name is written to the buffer. However, the check for whether the content->name     actually fits also uses 'len' rather than the updated buffer length strlen(buf). This allows us to write     about size many bytes beyond the allocated memory. This vulnerability causes programs that use libxml2,     such as PHP, to crash. (CVE-2017-9047)

  - libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a stack-based buffer overflow. The function     xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a     char buffer 'buf' of size 'size'. At the end of the routine, the function may strcat two more characters     without checking whether the current strlen(buf) + 2 < size. This vulnerability causes programs that use     libxml2, such as PHP, to crash. (CVE-2017-9048)

  - libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the     xmlDictComputeFastKey function in dict.c. This vulnerability causes programs that use libxml2, such as     PHP, to crash. This vulnerability exists because of an incomplete fix for libxml2 Bug 759398.
    (CVE-2017-9049)

  - libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the xmlDictAddString     function in dict.c. This vulnerability causes programs that use libxml2, such as PHP, to crash. This     vulnerability exists because of an incomplete fix for CVE-2016-1839. (CVE-2017-9050)

  - A NULL pointer dereference vulnerability exists in the xpath.c:xmlXPathCompOpEval() function of libxml2     through 2.9.8 when parsing an invalid XPath expression in the XPATH_OP_AND or XPATH_OP_OR case.
    Applications processing untrusted XSL format inputs with the use of the libxml2 library may be vulnerable     to a denial of service attack due to a crash of the application. (CVE-2018-14404)

  - xmlParseBalancedChunkMemoryRecover in parser.c in libxml2 before 2.9.10 has a memory leak related to     newDoc->oldNs. (CVE-2019-19956)

  - GNOME project libxml2 v2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at     libxml2/entities.c. The issue has been fixed in commit 50f06b3e. (CVE-2020-24977)

  - xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file     situation. (CVE-2020-7595)

  - There's a flaw in libxml2's xmllint in versions before 2.9.11. An attacker who is able to submit a crafted     file to be processed by xmllint could trigger a use-after-free. The greatest impact of this flaw is to     confidentiality, integrity, and availability. (CVE-2021-3516)

  - There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker     who is able to supply a crafted file to be processed by an application linked with the affected     functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to     application availability, with some potential impact to confidentiality and integrity if an attacker is     able to use memory information to further exploit the application. (CVE-2021-3517)

  - There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to     be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact     from this flaw is to confidentiality, integrity, and availability. (CVE-2021-3518)

  - A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while     parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery     mode and post-validated, the flaw could be used to crash the application. The highest threat from this     vulnerability is to system availability. (CVE-2021-3537)

  - A flaw was found in libxml2. Exponential entity expansion attack its possible bypassing all existing     protection mechanisms and leading to denial of service. (CVE-2021-3541)

  - valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes. (CVE-2022-23308)

  - In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*)     don't check for integer overflows. This can result in out-of-bounds memory writes. Exploitation requires a     victim to open a crafted, multi-gigabyte XML file. Other software using libxml2's buffer functions, for     example libxslt through 1.1.35, is affected as well. (CVE-2022-29824)

  - An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the     XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to     access an array at a negative 2GB offset, typically leading to a segmentation fault. (CVE-2022-40303)

  - An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a     hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be     provoked. (CVE-2022-40304)

  - In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference     and subsequently a segfault. This occurs in xmlSchemaFixupComplexType in xmlschemas.c. (CVE-2023-28484)

  - An issue was discovered in libxml2 before 2.10.4. When hashing empty dict strings in a crafted XML     document, xmlDictComputeFastKey in dict.c can produce non-deterministic values, leading to various logic     and memory errors, such as a double free. This behavior occurs because there is an attempt to use the     first byte of an empty string, and any value is possible (not solely the '\0' value). (CVE-2023-29469)

  - Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement()     function at /libxml2/SAX2.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via     supplying a crafted XML file. NOTE: the vendor's position is that the product does not support the legacy     SAX1 interface with custom callbacks; there is a crash even without crafted input. (CVE-2023-39615)

  - libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails.
    This occurs in xmlUnlinkNode in tree.c. NOTE: the vendor's position is I don't think these issues are     critical enough to warrant a CVE ID ... because an attacker typically can't control when memory     allocations fail. (CVE-2023-45322)

  - An issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5. When using the XML Reader     interface with DTD validation and XInclude expansion enabled, processing crafted XML documents can lead to     an xmlValidatePopElement use-after-free. (CVE-2024-25062)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

The remote Redhat Enterprise Linux 7 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - libxml2: Missing validation for external entities in xmlParsePEReference (CVE-2017-7375)

  - libxml2: Heap-based buffer overflow in xmlEncodeEntitiesInternal() in entities.c (CVE-2021-3517)

  - Possible cross-site scripting vulnerability in libxml after commit 960f0e2. (CVE-2016-3709)

  - The xmlBufAttrSerializeTxtContent function in xmlsave.c in libxml2 allows context-dependent attackers to     cause a denial of service (out-of-bounds read and application crash) via a non-UTF-8 attribute value,     related to serialization. NOTE: this vulnerability may be a duplicate of CVE-2016-3627. (CVE-2016-4483)

  - libxml2 2.9.4 and earlier, as used in XMLSec 1.2.23 and earlier and other products, does not offer a flag     directly indicating that the current document may be read but other files may not be opened, which makes     it easier for remote attackers to conduct XML External Entity (XXE) attacks via a crafted document.
    (CVE-2016-9318)

  - A remote code execution vulnerability in libxml2 could enable an attacker using a specially crafted file     to execute arbitrary code within the context of an unprivileged process. This issue is rated as High due     to the possibility of remote code execution in an application that uses this library. Product: Android.
    Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2. Android ID: A-37104170. (CVE-2017-0663)

  - parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the     xmlParserHandlePEReference function in the case of a '%' character in a DTD name. (CVE-2017-16931)

  - parser.c in libxml2 before 2.9.5 does not prevent infinite recursion in parameter entities.
    (CVE-2017-16932)

  - libxml2 2.9.4, when used in recover mode, allows remote attackers to cause a denial of service (NULL     pointer dereference) via a crafted XML document. NOTE: The maintainer states I would disagree of a CVE     with the Recover parsing option which should only be used for manual recovery at least for XML parser.
    (CVE-2017-5969)

  - The htmlParseTryOrFinish function in HTMLparser.c in libxml2 2.9.4 allows attackers to cause a denial of     service (buffer over-read) or information disclosure. (CVE-2017-8872)

  - A buffer overflow was discovered in libxml2 20904-GITv2.9.4-16-g0741801. The function     xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a     char buffer 'buf' of size 'size'. The variable len is assigned strlen(buf). If the content->type is     XML_ELEMENT_CONTENT_ELEMENT, then (i) the content->prefix is appended to buf (if it actually fits)     whereupon (ii) content->name is written to the buffer. However, the check for whether the content->name     actually fits also uses 'len' rather than the updated buffer length strlen(buf). This allows us to write     about size many bytes beyond the allocated memory. This vulnerability causes programs that use libxml2,     such as PHP, to crash. (CVE-2017-9047)

  - libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a stack-based buffer overflow. The function     xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a     char buffer 'buf' of size 'size'. At the end of the routine, the function may strcat two more characters     without checking whether the current strlen(buf) + 2 < size. This vulnerability causes programs that use     libxml2, such as PHP, to crash. (CVE-2017-9048)

  - libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the     xmlDictComputeFastKey function in dict.c. This vulnerability causes programs that use libxml2, such as     PHP, to crash. This vulnerability exists because of an incomplete fix for libxml2 Bug 759398.
    (CVE-2017-9049)

  - libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the xmlDictAddString     function in dict.c. This vulnerability causes programs that use libxml2, such as PHP, to crash. This     vulnerability exists because of an incomplete fix for CVE-2016-1839. (CVE-2017-9050)

  - There's a flaw in libxml2's xmllint in versions before 2.9.11. An attacker who is able to submit a crafted     file to be processed by xmllint could trigger a use-after-free. The greatest impact of this flaw is to     confidentiality, integrity, and availability. (CVE-2021-3516)

  - There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to     be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact     from this flaw is to confidentiality, integrity, and availability. (CVE-2021-3518)

  - A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while     parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery     mode and post-validated, the flaw could be used to crash the application. The highest threat from this     vulnerability is to system availability. (CVE-2021-3537)

  - valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes. (CVE-2022-23308)

  - An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the     XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to     access an array at a negative 2GB offset, typically leading to a segmentation fault. (CVE-2022-40303)

  - An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a     hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be     provoked. (CVE-2022-40304)

  - In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference     and subsequently a segfault. This occurs in xmlSchemaFixupComplexType in xmlschemas.c. (CVE-2023-28484)

  - An issue was discovered in libxml2 before 2.10.4. When hashing empty dict strings in a crafted XML     document, xmlDictComputeFastKey in dict.c can produce non-deterministic values, leading to various logic     and memory errors, such as a double free. This behavior occurs because there is an attempt to use the     first byte of an empty string, and any value is possible (not solely the '\0' value). (CVE-2023-29469)

  - Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement()     function at /libxml2/SAX2.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via     supplying a crafted XML file. NOTE: the vendor's position is that the product does not support the legacy     SAX1 interface with custom callbacks; there is a crash even without crafted input. (CVE-2023-39615)

  - An issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5. When using the XML Reader     interface with DTD validation and XInclude expansion enabled, processing crafted XML documents can lead to     an xmlValidatePopElement use-after-free. (CVE-2024-25062)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

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

  - The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.6.2, macOS     Ventura 13.1. An app may be able to disclose kernel memory. (CVE-2022-42854)

  - A logic issue was addressed with improved checks. This issue is fixed in macOS Monterey 12.6.2, macOS Big     Sur 11.7.2, macOS Ventura 13. An app may bypass Gatekeeper checks. (CVE-2022-42821)

  - An access issue was addressed with improved access restrictions. This issue is fixed in macOS Ventura     13.1. An app may be able to modify protected parts of the file system. (CVE-2022-42853)

  - The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.6.2, macOS     Ventura 13.1, macOS Big Sur 11.7.2. An app may be able to execute arbitrary code with kernel privileges.
    (CVE-2022-32942)

  - This issue was addressed with improved checks. This issue is fixed in iOS 16.2 and iPadOS 16.2, macOS     Monterey 12.6.2, macOS Ventura 13.1, iOS 15.7.2 and iPadOS 15.7.2. An app may be able to break out of its     sandbox. (CVE-2022-42861)

  - A race condition was addressed with improved state handling. This issue is fixed in tvOS 16.2, macOS     Monterey 12.6.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, iOS 15.7.2 and iPadOS 15.7.2, iOS 16.2 and     iPadOS 16.2, watchOS 9.2. An app may be able to execute arbitrary code with kernel privileges.
    (CVE-2022-42864)

  - A race condition was addressed with additional validation. This issue is fixed in tvOS 16.2, macOS     Monterey 12.6.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, iOS 15.7.2 and iPadOS 15.7.2, iOS 16.2 and     iPadOS 16.2, watchOS 9.2. An app may be able to execute arbitrary code with kernel privileges.
    (CVE-2022-46689)

  - The issue was addressed with improved memory handling. This issue is fixed in tvOS 16.2, macOS Monterey     12.6.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, iOS 16.2 and iPadOS 16.2, watchOS 9.2. An app with root     privileges may be able to execute arbitrary code with kernel privileges. (CVE-2022-42845)

  - The issue was addressed with improved memory handling. This issue is fixed in tvOS 16.2, macOS Monterey     12.6.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, iOS 16.2 and iPadOS 16.2, watchOS 9.2. A remote user may     be able to cause kernel code execution. (CVE-2022-42842)

  - An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the     XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to     access an array at a negative 2GB offset, typically leading to a segmentation fault. (CVE-2022-40303)

  - An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a     hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be     provoked. (CVE-2022-40304)

  - A logic issue was addressed with improved state management. This issue is fixed in macOS Ventura 13.1,     macOS Big Sur 11.7.2, macOS Monterey 12.6.2. An app may be able to modify protected parts of the file     system. (CVE-2022-46704)

  - The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.6.2, macOS     Ventura 13.1, macOS Big Sur 11.7.2, iOS 15.7.2 and iPadOS 15.7.2, iOS 16.2 and iPadOS 16.2. An app may be     able to execute arbitrary code with kernel privileges. (CVE-2022-42840)

  - A logic issue was addressed with improved state management. This issue is fixed in tvOS 16.2, macOS     Monterey 12.6.2, macOS Ventura 13.1, iOS 15.7.2 and iPadOS 15.7.2, iOS 16.2 and iPadOS 16.2. An app may be     able to use arbitrary entitlements. (CVE-2022-42855)

  - A logic issue was addressed with improved restrictions. This issue is fixed in iOS 15.7.2 and iPadOS     15.7.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, macOS Monterey 12.6.2. An app may be able to read     sensitive location information (CVE-2022-46718)

  - A logic issue was addressed with improved restrictions. This issue is fixed in iOS 15.7.2 and iPadOS     15.7.2, macOS Ventura 13.1, iOS 16.2 and iPadOS 16.2. An app may be able to read sensitive location     information (CVE-2022-46703)

  - A type confusion issue was addressed with improved checks. This issue is fixed in macOS Monterey 12.6.2,     macOS Ventura 13.1, macOS Big Sur 11.7.2. Processing a maliciously crafted package may lead to arbitrary     code execution. (CVE-2022-42841)

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 11.x prior to 11.7.2. It is, therefore, affected by multiple vulnerabilities:

  - This issue was addressed by enabling hardened runtime. This issue is fixed in iOS 16.2 and iPadOS 16.2,     macOS Ventura 13.1, tvOS 16.2, watchOS 9.2. An app may be able to bypass Privacy preferences.
    (CVE-2022-42865)

  - A logic issue was addressed with improved checks. This issue is fixed in macOS Monterey 12.6.2, macOS Big     Sur 11.7.2, macOS Ventura 13. An app may bypass Gatekeeper checks. (CVE-2022-42821)

  - The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.6.2, macOS     Ventura 13.1, macOS Big Sur 11.7.2. An app may be able to execute arbitrary code with kernel privileges.
    (CVE-2022-32942)

  - A race condition was addressed with improved state handling. This issue is fixed in tvOS 16.2, macOS     Monterey 12.6.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, iOS 15.7.2 and iPadOS 15.7.2, iOS 16.2 and     iPadOS 16.2, watchOS 9.2. An app may be able to execute arbitrary code with kernel privileges.
    (CVE-2022-42864)

  - A race condition was addressed with additional validation. This issue is fixed in tvOS 16.2, macOS     Monterey 12.6.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, iOS 15.7.2 and iPadOS 15.7.2, iOS 16.2 and     iPadOS 16.2, watchOS 9.2. An app may be able to execute arbitrary code with kernel privileges.
    (CVE-2022-46689)

  - The issue was addressed with improved memory handling. This issue is fixed in tvOS 16.2, macOS Monterey     12.6.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, iOS 16.2 and iPadOS 16.2, watchOS 9.2. An app with root     privileges may be able to execute arbitrary code with kernel privileges. (CVE-2022-42845)

  - The issue was addressed with improved memory handling. This issue is fixed in tvOS 16.2, macOS Monterey     12.6.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, iOS 16.2 and iPadOS 16.2, watchOS 9.2. A remote user may     be able to cause kernel code execution. (CVE-2022-42842)

  - An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the     XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to     access an array at a negative 2GB offset, typically leading to a segmentation fault. (CVE-2022-40303)

  - An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a     hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be     provoked. (CVE-2022-40304)

  - A logic issue was addressed with improved state management. This issue is fixed in macOS Ventura 13.1,     macOS Big Sur 11.7.2, macOS Monterey 12.6.2. An app may be able to modify protected parts of the file     system. (CVE-2022-46704)

  - The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.6.2, macOS     Ventura 13.1, macOS Big Sur 11.7.2, iOS 15.7.2 and iPadOS 15.7.2, iOS 16.2 and iPadOS 16.2. An app may be     able to execute arbitrary code with kernel privileges. (CVE-2022-42840)

  - A logic issue was addressed with improved restrictions. This issue is fixed in iOS 15.7.2 and iPadOS     15.7.2, macOS Ventura 13.1, macOS Big Sur 11.7.2, macOS Monterey 12.6.2. An app may be able to read     sensitive location information (CVE-2022-46718)

  - A type confusion issue was addressed with improved checks. This issue is fixed in macOS Monterey 12.6.2,     macOS Ventura 13.1, macOS Big Sur 11.7.2. Processing a maliciously crafted package may lead to arbitrary     code execution. (CVE-2022-42841)

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

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

ID	Name	Product	Family	Published	Updated	Severity
178854	EulerOS Virtualization 3.0.6.6 : libxml2 (EulerOS-SA-2023-2412)	Nessus	Huawei Local Security Checks	7/26/2023	7/26/2023	high
185073	Rocky Linux 9 : libxml2 (RLSA-2023:0338)	Nessus	Rocky Linux Local Security Checks	11/7/2023	11/7/2023	high
190175	CentOS 8 : libxml2 (CESA-2023:0173)	Nessus	CentOS Local Security Checks	2/8/2024	2/8/2024	high
195344	RHEL 6 : libxml2 (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	5/11/2024	5/11/2024	critical
195373	RHEL 7 : libxml2 (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	5/11/2024	5/11/2024	critical
168669	macOS 12.x < 12.6.2 Multiple Vulnerabilities (HT213533)	Nessus	MacOS X Local Security Checks	12/13/2022	1/24/2024	critical
168670	macOS 11.x < 11.7.2 Multiple Vulnerabilities (HT213534)	Nessus	MacOS X Local Security Checks	12/13/2022	1/24/2024	critical
169649	Apple TV < 16.2 Multiple Vulnerabilities (HT213535)	Nessus	Misc.	1/6/2023	2/1/2024	critical

Detections

Analytics

Plugins Search

high

high

high

critical

critical

critical

critical

critical