Saelo

A memory corruption issue exists due to improper memory handling, which was addressed with improved memory handling. The issue also involves an improper access check privilege escalation.

A cross-site scripting issue existed in Safari, which was addressed with improved URL validation.

The issue is related to multiple memory corruption problems that have been addressed through improved memory handling.

The issue involves the `libxpc` component and allows attackers to gain privileges via a crafted app that leverages a logic error.

This issue allows remote attackers to disclose sensitive information on vulnerable installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of typed arrays due to the lack of proper initialization of a pointer prior to accessing it. An attacker can leverage this, in conjunction with other issues, to execute code in the context of the current process.

The issue involves the WebKit component and allows remote attackers to execute arbitrary code or cause a denial of service, resulting in memory corruption and application crash, via a crafted web site.

The issue is related to a use after free vulnerability in the String.replace method in JavaScriptCore. This allows remote attackers to execute arbitrary code via a crafted web page or a crafted file. The vulnerability was demonstrated at Pwn2Own, indicating its potential for real-world exploitation.

The issue allows remote attackers to cause a denial of service and execute arbitrary code via a chunked Transfer-Encoding request with a large chunk size. This triggers an integer signedness error and a stack-based buffer overflow.

The issue involves the WebKit component and allows remote attackers to execute arbitrary code or cause a denial of service, resulting in memory corruption and application crash, via a crafted web site.