Nik Tsytsarkin

An out-of-bounds write occurs due to insufficient input validation. This flaw allows an application to corrupt kernel memory or cause unexpected system termination.

Processing a maliciously crafted image may result in disclosure of process memory.

An out-of-bounds write issue occurs due to insufficient bounds checking. Processing a maliciously crafted video file can lead to unexpected app termination. An out-of-bounds write is a condition where the program writes data past the end of the intended buffer, potentially corrupting memory.

An out-of-bounds write issue occurs when processing a maliciously crafted 3D model, which may lead to memory corruption. This is caused by insufficient bounds checking during the processing of the model data.

A buffer overflow occurs when a program writes more data to a block of memory than it can hold. Processing a maliciously crafted image may lead to unexpected process termination.

Processing a maliciously crafted 3D model may lead to memory corruption, which occurs when a program accidentally writes data to the wrong memory address, potentially causing crashes or unexpected behavior.

A buffer overflow occurs when a program writes more data to a memory buffer than it can hold, potentially overwriting adjacent memory. Processing a maliciously crafted image can lead to process memory corruption.

An out-of-bounds read occurs when a program reads data outside the intended boundary of a buffer. Processing a maliciously crafted image may result in the disclosure of process memory.

An out-of-bounds write issue occurs due to insufficient bounds checking. Processing a maliciously crafted PDF file may lead to memory corruption, which happens when a program writes data outside the boundaries of a pre-allocated memory buffer.

An out-of-bounds write issue occurs due to insufficient bounds checking. Processing a maliciously crafted PDF file may lead to memory corruption, which happens when a program writes data outside the boundaries of a pre-allocated memory buffer.

An out-of-bounds read occurs when a program reads data outside the intended boundary of a buffer. Processing a maliciously crafted font may result in the disclosure of process memory.

A buffer overflow issue exists where an app may cause unexpected system termination or corrupt process memory. This occurs due to insufficient memory handling.

An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2 and iPadOS 27.2, visionOS 27.2, watchOS 27.2. A buffer overflow may result in memory corruption and unexpected app termination.

An authentication issue was addressed with improved state management. This issue is fixed in iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2 and iPadOS 27.2. A malicious app may be able to access Bluetooth without user consent.

An out-of-bounds write issue exists where an application can write to kernel memory or cause unexpected system termination. This occurs due to insufficient bounds checking, which is a process of verifying that a program does not access memory outside the boundaries of a predefined buffer.

Improper access control in Windows Kernel-Mode Drivers allows an authorized attacker to elevate privileges locally, which can lead to full system compromise.

A use after free issue, which occurs when a program continues to use a pointer after it has been freed, can lead to unexpected system termination if triggered by an app.

A logic issue exists where an app may be able to leak sensitive user information. This was addressed by implementing improved checks.

A flaw exists in the Opto22 Groov Manage REST API that could allow for remote code execution with root privileges. The issue arises when a POST request is sent to a vulnerable endpoint. The application improperly handles header details from the request, using them to construct commands without sufficient safeguards. This allows an attacker with administrative access to inject and execute arbitrary commands as root. The vulnerable endpoint processes POST requests and utilizes header information to build commands. The vulnerable parameters are within the request headers.