Inooo

**Name of the Vulnerable Software and Affected Versions** FreeBSD versions 12.4-RELEASE prior to 12.4-RELEASE-p7 FreeBSD versions 13.2-RELEASE prior to 13.2-RELEASE-p5 **Description** The sflush() stdio function in libc does not correctly update FILE objects' write space members for write-buffered streams when the write(2) system call returns an error. Depending on the nature of an application that calls libc's stdio functions and the presence of errors returned from the write(2) system call, a heap buffer overflow may occur. Such overflows may lead to data corruption or the execution of arbitrary code at the privilege level of the calling program. **Recommendations** For FreeBSD versions 12.4-RELEASE prior to 12.4-RELEASE-p7, update to 12.4-RELEASE-p7 or later. For FreeBSD versions 13.2-RELEASE prior to 13.2-RELEASE-p5, update to 13.2-RELEASE-p5 or later. As a temporary workaround, consider restricting the use of the sflush() function in libc until a patch is available.

**Name of the Vulnerable Software and Affected Versions** macOS Monterey versions prior to 12.7.1 iOS versions prior to 16.7.2 and prior to 17.1 iPadOS versions prior to 16.7.2 and prior to 17.1 **Description** The issue is related to improved memory handling and may lead to arbitrary code execution in user-installed apps when processing maliciously crafted input. It is associated with a buffer overflow in the libc component of the operating systems. **Recommendations** For macOS Monterey versions prior to 12.7.1, update to macOS Monterey 12.7.1 or later. For iOS versions prior to 16.7.2, update to iOS 16.7.2 or later. For iOS versions prior to 17.1, update to iOS 17.1 or later. For iPadOS versions prior to 16.7.2, update to iPadOS 16.7.2 or later. For iPadOS versions prior to 17.1, update to iPadOS 17.1 or later.

**Name of the Vulnerable Software and Affected Versions** iperf3 versions prior to 3.14 **Description** The issue is related to an integer overflow when handling field lengths, which can be exploited by a remote attacker to cause a denial of service. This can lead to heap corruption via a crafted length field. **Recommendations** For versions prior to 3.14, update to version 3.14 or later to resolve the issue. As a temporary workaround, consider restricting access to the `iperf3` tool until a patch is applied.