Marcograss

The issue involves the CoreGraphics 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 JPEG file. This is caused by a buffer overflow in the CoreGraphics component of Mac OS X and iOS operating systems.

The issue involves the `WebSheet` component, which allows attackers to bypass a sandbox protection mechanism via unspecified vectors. This is related to errors in security settings, potentially enabling a remote attacker to exploit the issue and bypass the sandbox protection.

The issue is related to insufficient access control in the Intel graphics driver of Mac OS X, which can be exploited by a local attacker to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) using a specially crafted application.

The issue is related to errors in security settings of the Intel Graphics Driver component in Mac OS X, allowing a remote attacker to obtain sensitive kernel memory-layout information using a specially crafted app.

The issue allows attackers to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) via a crafted app. It is caused by a buffer overflow in the IOFireWireFamily component.

The issue is caused by a buffer overflow in the IOHIDFamily component of iOS and Mac OS X operating systems. Exploitation of this issue may allow a remote attacker to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) using a specially crafted application.

The issue allows attackers to obtain sensitive information and bypass an unspecified protection mechanism via unknown vectors. This can be demonstrated by obtaining Signature or SignatureOrSystem access. The vulnerability is related to the lack of protection for service data, which can allow a remote attacker to obtain confidential information or bypass protection mechanisms.

The issue is related to a stack-based buffer overflow in the `havok write` function. This can be exploited by sending a long string to the `/dev/hv` device, potentially causing a denial of service or other unspecified impacts.