Jihwan Kim

**Name of the Vulnerable Software and Affected Versions** PHP versions prior to 8.1.33 PHP versions prior to 8.2.29 PHP versions prior to 8.3.23 PHP versions prior to 8.4.10 PHP 7.4 (affected versions not specified) PHP 8.2 (affected versions not specified) **Description** PHP versions 8.1.* before 8.1.33, 8.2.* before 8.2.29, 8.3.* before 8.3.23, and 8.4.* before 8.4.10 are susceptible to a null character injection issue. Specifically, functions such as `fsockopen()` do not properly validate hostnames for null characters. This can cause functions like `parse url()` to interpret the hostname incorrectly, potentially leading to security problems if user code implements access checks before accessing resources. This could result in denial of service or server-side request forgery (SSRF). **Recommendations** Upgrade to PHP version 8.1.33 or later. Upgrade to PHP version 8.2.29 or later. Upgrade to PHP version 8.3.23 or later. Upgrade to PHP version 8.4.10 or later. Upgrade your php8.2 packages to version 8.2.29-1~deb12u1 or later. Upgrade your php7.4 packages to the latest available version.

**Name of the Vulnerable Software and Affected Versions** Safari versions prior to 16.1 tvOS versions prior to 16.1 macOS Ventura versions prior to 13 watchOS versions prior to 9.1 iOS versions prior to 16.1 iPadOS versions prior to 16.1 **Description** The issue is related to incorrect restriction of visualizable user interface layers in WebKit, which may lead to user interface spoofing when visiting a malicious website. This could allow a remote attacker to access and compromise confidential data. **Recommendations** For Safari versions prior to 16.1, update to Safari 16.1 to resolve the issue. For tvOS versions prior to 16.1, update to tvOS 16.1 to resolve the issue. For macOS Ventura versions prior to 13, update to macOS Ventura 13 to resolve the issue. For watchOS versions prior to 9.1, update to watchOS 9.1 to resolve the issue. For iOS versions prior to 16.1, update to iOS 16.1 to resolve the issue. For iPadOS versions prior to 16.1, update to iPadOS 16.1 to resolve the issue.