Elvanderb

**Name of the Vulnerable Software and Affected Versions** macOS versions prior to 14.2 iOS versions prior to 17.2 iPadOS versions prior to 17.2 watchOS versions prior to 10.2 tvOS versions prior to 17.2 macOS Ventura versions prior to 13.6.3 macOS Monterey versions prior to 12.7.2 iOS versions prior to 16.7.3 iPadOS versions prior to 16.7.3 **Description** The issue is related to a buffer overflow in memory, which may allow an attacker to bypass security restrictions. An app may be able to break out of its sandbox. The issue was addressed with improved memory handling. **Recommendations** For macOS versions prior to 14.2, update to macOS Sonoma 14.2 or later. For iOS versions prior to 17.2, update to iOS 17.2 or later. For iPadOS versions prior to 17.2, update to iPadOS 17.2 or later. For watchOS versions prior to 10.2, update to watchOS 10.2 or later. For tvOS versions prior to 17.2, update to tvOS 17.2 or later. For macOS Ventura versions prior to 13.6.3, update to macOS Ventura 13.6.3 or later. For macOS Monterey versions prior to 12.7.2, update to macOS Monterey 12.7.2 or later. For iOS versions prior to 16.7.3, update to iOS 16.7.3 or later. For iPadOS versions prior to 16.7.3, update to iPadOS 16.7.3 or later.

**Name of the Vulnerable Software and Affected Versions** Cisco WAP4410N access point versions 2.0.6.1 and earlier Cisco WRVS4400N router versions 1.1.13 and earlier, versions 2.0.2.1 and earlier Cisco RVS4000 router versions 2.0.3.2 and earlier **Description** The issue allows remote attackers to read credential and configuration data and execute arbitrary commands via requests to the test interface on TCP port 32764. **Recommendations** For Cisco WAP4410N access point versions 2.0.6.1 and earlier, update the firmware to a version later than 2.0.6.1. For Cisco WRVS4400N router versions 1.1.13 and earlier, update the firmware to a version later than 1.1.13. For Cisco WRVS4400N router versions 2.0.2.1 and earlier, update the firmware to a version later than 2.0.2.1. For Cisco RVS4000 router versions 2.0.3.2 and earlier, update the firmware to a version later than 2.0.3.2. As a temporary workaround, consider restricting access to the test interface on TCP port 32764 until a patch is available.