Todd Manning

The Cowork VM image handling process validates only the presence of the file and a version marker string before booting `rootfs.img`, failing to verify the integrity of the image content at the time of use. A local attacker with unprivileged code execution as the victim macOS user can modify the VM root filesystem image to ensure it is trusted during subsequent boots. This allows for persistent arbitrary code execution within the VM and unauthorized access to host-mounted directories. This issue is characterized by a missing support for integrity check, which is a failure to verify that data has not been altered by an unauthorized party.

This issue allows network-adjacent attackers to disclose sensitive information on affected installations of ChargePoint Home Flex charging devices. The specific flaw exists within the Wi-Fi setup logic. By connecting to the device over Bluetooth Low Energy during the setup process, an attacker can obtain Wi-Fi credentials. An attacker can leverage this issue to disclose credentials and gain access to the device owner's Wi-Fi network. User interaction is required to exploit this issue.

This issue allows network-adjacent attackers to create a denial-of-service condition on affected installations of ChargePoint Home Flex charging devices. The specific flaw exists within the connection handling of the Bluetooth Low Energy interface, where limiting the number of active connections to the product can be exploited to create a denial-of-service condition. Authentication is not required to exploit this issue.

A local attacker with low privileges can perform a privilege escalation with an init script due to a Time-of-Check-to-Time-of-Use (TOCTOU) vulnerability.

The issue allows multiple vulnerabilities to be exploited when a valid user opens a specially crafted, malicious input file that operates outside of the designated memory area, potentially leading to information disclosure, memory corruption, and remote code execution.

The issue allows for exploitation when a valid user opens a specially crafted, malicious input file. This can lead to referencing memory after it has been freed, which is a use-after-free condition. This condition can potentially be used for remote code execution or information disclosure.

The issue allows an attacker to access configuration files due to the use of a hard-coded password for encrypting protected files in transit and at rest.

The issue allows multiple vulnerabilities to be exploited when a valid user opens a specially crafted, malicious input file, causing the program to mishandle pointers. This can lead to remote code execution due to untrusted pointer dereference.