Kasif Dekel

The issue is related to incorrect code generation management in Microsoft Defender for IoT, which can be exploited by a remote attacker to execute arbitrary code using a specially crafted request.

The issue is related to insufficient access control in Microsoft Defender for IoT, which can be exploited to elevate privileges in the system.

The issue allows local attackers to execute arbitrary code in kernel mode or cause a denial of service, resulting in memory corruption and OS crash, via specially crafted I/O Request Packet. This is due to an Integer Overflow in the IOCTL Handler 0x22001B.

Name of the Vulnerable Software and Affected Versions: Amazon WorkSpaces agent versions prior to 1.0.1.1537 Description: The issue is related to an Integer Overflow in the Amazon WorkSpaces agent. It affects the IOCTL Handler 0x22001B, allowing local attackers to execute arbitrary code in kernel mode or cause a denial of service, resulting in memory corruption and OS crash, via specially crafted I/O Request Packets. Recommendations: For versions prior to 1.0.1.1537, update to version 1.0.1.1537 or later to resolve the issue. As a temporary workaround, consider restricting access to the IOCTL Handler 0x22001B to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Amazon WorkSpaces agent versions prior to 1.0.1.1537 Description: The issue is related to a Buffer Overflow in the Amazon WorkSpaces agent. It affects the IOCTL Handler 0x22001B, allowing local attackers to execute arbitrary code in kernel mode or cause a denial of service, such as memory corruption and OS crash, via specially crafted I/O Request Packets. Recommendations: For versions prior to 1.0.1.1537, update to version 1.0.1.1537 or later to resolve the issue. As a temporary workaround, consider restricting access to the IOCTL Handler 0x22001B to minimize the risk of exploitation.

A Buffer Overflow issue exists, allowing local attackers to execute arbitrary code in kernel mode or cause a denial of service via specially crafted I/O Request Packets. The IOCTL Handler 0x22001B is involved in this issue, potentially leading to memory corruption and OS crash.

An Integer Overflow issue exists, allowing local attackers to execute arbitrary code in kernel mode or cause a denial of service via specially crafted I/O Request Packets. The IOCTL Handler 0x22001B is affected, potentially leading to memory corruption and OS crash.

A Buffer Overflow issue exists, allowing local attackers to execute arbitrary code in kernel mode or cause a denial of service via specially crafted I/O Request Packets. The IOCTL Handler 0x22001B is involved in this issue, potentially leading to memory corruption and OS crash.

An Integer Overflow issue exists, allowing local attackers to execute arbitrary code in kernel mode or cause a denial of service via specially crafted I/O Request Packets. The IOCTL Handler 0x22005B is affected, potentially leading to memory corruption and OS crashes.

An Integer Overflow exists in the Accops HyWorks Windows Client, allowing local attackers to execute arbitrary code in kernel mode or cause a denial of service via specially crafted I/O Request Packets. The IOCTL Handler 0x22001B is affected, potentially leading to memory corruption and OS crash.

A Buffer Overflow issue exists, allowing local attackers to execute arbitrary code in kernel mode or cause a denial of service via specially crafted I/O Request Packets. The IOCTL Handler 0x22005B is vulnerable, potentially leading to memory corruption and OS crash.

An Integer Overflow issue exists, allowing local attackers to execute arbitrary code in kernel mode or cause a denial of service via specially crafted I/O Request Packets. The IOCTL Handler 0x22005B is affected, potentially leading to memory corruption and OS crash.

The issue allows local attackers to execute arbitrary code in kernel mode or cause a denial of service, such as memory corruption and OS crash, via specially crafted I/O Request Packet. This is due to a Buffer Overflow in the IOCTL Handler 0x22001B.

The issue is related to an Integer Overflow in the NoMachine Server. Specifically, the IOCTL Handler 0x22001B is vulnerable, allowing local attackers to execute arbitrary code in kernel mode or cause a denial of service, resulting in memory corruption and OS crash, via specially crafted I/O Request Packets.

The issue allows local attackers to execute arbitrary code in kernel mode or cause a denial of service, resulting in memory corruption and OS crash, via specially crafted I/O Request Packet. This is due to a Buffer Overflow in the IOCTL Handler 0x22001B.

The issue allows local attackers to execute arbitrary code in kernel mode or cause a denial of service, resulting in memory corruption and OS crash, via specially crafted I/O Request Packet. This is due to an Integer Overflow in the IOCTL Handler 0x22001B.

The issue allows local attackers to execute arbitrary code in kernel mode or cause a denial of service, resulting in memory corruption and OS crash, via specially crafted I/O Request Packet. This is due to an Integer Overflow in the IOCTL Handler 0x22001B.

The issue allows local attackers to execute arbitrary code in kernel mode or cause a denial of service, such as memory corruption and OS crash, via specially crafted I/O Request Packet. This is due to a Buffer Overflow in the IOCTL Handler 0x22001B.

The issue allows local attackers to execute arbitrary code in kernel mode or cause a denial of service, resulting in memory corruption and OS crash, via specially crafted I/O Request Packet. This is due to a Buffer Overflow in the IOCTL Handler 0x22001B.

The issue allows local attackers to execute arbitrary code in kernel mode or cause a denial of service, resulting in memory corruption and OS crash, via specially crafted I/O Request Packet. This is due to an Integer Overflow in the IOCTL Handler 0x22001B.