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

  - A use after free issue was addressed with improved memory management. This issue is fixed in visionOS 2.3,     iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3, watchOS 11.3, tvOS 18.3. A malicious application may be able     to elevate privileges. Apple is aware of a report that this issue may have been actively exploited against     versions of iOS before iOS 17.2. (CVE-2025-24085)

  - The issue was addressed with improved handling of protocols. This issue is fixed in macOS Ventura 13.7.5,     macOS Sonoma 14.7.5. An attacker in a privileged network position can track a user's activity.
    (CVE-2024-40864)

  - A permissions issue was addressed with additional sandbox restrictions. This issue is fixed in macOS     Ventura 13.7.5, macOS Sonoma 14.7.5. An app may be able to access sensitive user data. (CVE-2024-54533)

  - libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and     xmlSchemaBubbleIDCNodeTables in xmlschemas.c. To exploit this, a crafted XML document must be validated     against an XML schema with certain identity constraints, or a crafted XML schema must be used.
    (CVE-2024-56171)

  - When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache     entry, making it end sooner or later than otherwise intended. This affects curl using applications that     enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like     `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS     cache either needs to have been populated manually or there needs to have been previous HTTPS accesses     done as the cache needs to have entries for the domains involved to trigger this problem.) When     `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's     expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The     result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different     period of time than what was asked for by the origin server. If `example.com` for example stops supporting     HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set)     timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently     switch back to insecure HTTP earlier than otherwise intended. (CVE-2024-9681)

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

  - A use after free issue was addressed with improved memory management. This issue is fixed in visionOS 2.3,     iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3, watchOS 11.3, tvOS 18.3. A malicious application may be able     to elevate privileges. Apple is aware of a report that this issue may have been actively exploited against     versions of iOS before iOS 17.2. (CVE-2025-24085)

  - The issue was addressed with improved handling of protocols. This issue is fixed in macOS Ventura 13.7.5,     macOS Sonoma 14.7.5. An attacker in a privileged network position can track a user's activity.
    (CVE-2024-40864)

  - A permissions issue was addressed with additional sandbox restrictions. This issue is fixed in macOS     Ventura 13.7.5, macOS Sonoma 14.7.5. An app may be able to access sensitive user data. (CVE-2024-54533)

  - libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and     xmlSchemaBubbleIDCNodeTables in xmlschemas.c. To exploit this, a crafted XML document must be validated     against an XML schema with certain identity constraints, or a crafted XML schema must be used.
    (CVE-2024-56171)

  - When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache     entry, making it end sooner or later than otherwise intended. This affects curl using applications that     enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like     `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS     cache either needs to have been populated manually or there needs to have been previous HTTPS accesses     done as the cache needs to have entries for the domains involved to trigger this problem.) When     `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's     expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The     result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different     period of time than what was asked for by the origin server. If `example.com` for example stops supporting     HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set)     timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently     switch back to insecure HTTP earlier than otherwise intended. (CVE-2024-9681)

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

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

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

  - An out-of-bounds write was addressed with improved input validation. This issue is fixed in macOS Ventura     13.7.3, macOS Sonoma 14.7.3, visionOS 2.3, iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3. An attacker may     be able to cause unexpected system termination or corrupt kernel memory. (CVE-2025-24154)

  - A privacy issue was addressed with improved handling of files. This issue is fixed in macOS Sequoia 15.3,     Safari 18.3, iOS 18.3 and iPadOS 18.3. Copying a URL from Web Inspector may lead to command injection.
    (CVE-2025-24150)

  - A use after free issue was addressed with improved memory management. This issue is fixed in visionOS 2.3,     iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3, watchOS 11.3, tvOS 18.3. A malicious application may be able     to elevate privileges. Apple is aware of a report that this issue may have been actively exploited against     versions of iOS before iOS 17.2. (CVE-2025-24085)

  - The issue was addressed with improved memory handling. This issue is fixed in iPadOS 17.7.4, macOS Ventura     13.7.3, macOS Sonoma 14.7.3, visionOS 2.3, iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3, watchOS 11.3,     tvOS 18.3. Processing an image may lead to a denial-of-service. (CVE-2025-24086)

  - The issue was addressed with additional permissions checks. This issue is fixed in macOS Sequoia 15.3. An     app may be able to access protected user data. (CVE-2025-24087)

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	Published	Updated	Severity
233569	macOS 13.x < 13.7.5 Multiple Vulnerabilities (122375)	Nessus	MacOS X Local Security Checks	3/31/2025	4/4/2025	high
233570	macOS 14.x < 14.7.5 Multiple Vulnerabilities (122374)	Nessus	MacOS X Local Security Checks	3/31/2025	4/4/2025	high
214658	Apple iOS < 18.3 Multiple Vulnerabilities (122066)	Nessus	Mobile Devices	1/27/2025	3/10/2025	critical
214659	macOS 15.x < 15.3 Multiple Vulnerabilities (122068)	Nessus	MacOS X Local Security Checks	1/27/2025	3/20/2025	critical

Detections

Analytics

Plugins Search

high

high

critical

critical