Oasis Security Identifies Security Weakness in Cursor AI Coding Tool - DevOps.com
Briefly

Oasis Security Identifies Security Weakness in Cursor AI Coding Tool - DevOps.com
"Oasis Security this week warned application developers of a security flaw in the Cursor artificial intelligence (AI) code editor developed by Anysphere, Inc. that potentially could be used to allow a maliciously crafted code repository to execute code as soon as it's opened using Cursor. Erez Schwartz, threat research engineer at Oasis Security, said that unlike other coding tools based on the open source Visual Studio (VS) Code tool originally developed by Microsoft, the Cursor AI tool disables a Workspace Trust feature by default."
"Additionally, Oasis Security is recommending that in addition to enabling Workspace Trust to run at startup, they should also consider setting task.allowAutomaticTasks to off and that any unknown repositories only be opened in a safe environment. They should also search for .vscode/tasks.json with "runOn": "folderOpen" and monitor any spawned shells and unusual outbound requests that occur immediately after opening a project."
A security flaw in the Cursor AI code editor can allow a maliciously crafted repository to execute code immediately when the project is opened. Cursor disables the Workspace Trust feature by default, creating potential for automatic task execution in unknown folders. Recommended mitigations include enabling Workspace Trust at startup, setting task.allowAutomaticTasks to off, opening unknown repositories within safe environments, and searching for .vscode/tasks.json entries with "runOn": "folderOpen". Monitoring spawned shells and unusual outbound requests after opening projects is advised. DevSecOps teams should enforce configuration controls and security policies for AI coding tools used by developers.
Read at DevOps.com
Unable to calculate read time
[
|
]