CVE-2024-45599 TCC Bypass in Cursor's macOS Application
Attackers can bypass macOS TCC restrictions to access camera and microphone via DyLib injection in Cursor, requiring prior user permission grants.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-45599?
CVE-2024-45599 is a low-severity vulnerability in getcursor cursor, published on 24 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Cursor is an artificial intelligence code editor. Prior to version 0.41.0, if a user on macOS has granted Cursor access to the camera or microphone, any program that is run on the machine is able to access the camera or the microphone without explicitly being granted access, through a DyLib Injection using DYLD_INSERT_LIBRARIES environment variable. The usage of `com.apple.security.cs.allow-dyld-environment-variables` and `com.apple.security.cs.disable-library-validation` allows an external dynamic library to be injected into the application using DYLD_INSERT_LIBRARIES environment variable. Moreover, the entitlement `com.apple.security.device.camera` allows the application to use the host camera and `com.apple.security.device.audio-input` allows the application to use the microphone. This means that untrusted code that is executed on the user's machine can access the camera or the microphone, if the user has already given permission for Cursor to do so. In version 0.41.0, the entitlements have been split by process: the main process gets the camera and microphone entitlements, but not the DyLib entitlements, whereas the extension host process gets the DyLib entitlements but not the camera or microphone entitlements. As a workaround, do not explicitly give Cursor the permission to access the camera or microphone if untrusted users can run arbitrary commands on the affected machine.
Weakness: CWE-277
Which versions are affected by CVE-2024-45599?
How do I fix CVE-2024-45599?
No fix has been published for CVE-2024-45599 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-45599 being exploited?
There is no known exploitation of CVE-2024-45599 in the wild and no public exploit code.