Impact
The Cody AI VSCode extension versions >=0.10.0 and <=0.14.0 are vulnerable to Remote Code Execution under certain conditions.
An attacker in control of a malicious repository could modify the Cody configuration file .vscode/cody.json and overwrite Cody commands. If a user with the extension installed opens this malicious repository and runs a Cody command such as /explain or /doc, this could allow arbitrary code execution on the user's machine.
The vulnerability is rated as critical severity, but with low exploitability. It requires the user to have a malicious repository loaded and execute the overwritten command in VS Code. The issue is exploitable regardless of the user blocking code execution on a repository through VS Code Workspace Trust.
The issue was found during a regular 3rd party penetration test. We do not have evidence of open source repositories having malicious .vscode/cody.json files to exploit this vulnerability.
Patches
The issue is fixed in version 0.14.1 of the Cody VSCode extension.
Reference
PR
Workarounds
In case users can't promptly upgrade they should not open any untrusted repositories with the Cody extension loaded.
You may use the following Sourcegraph search query to find repositories overwriting Cody commands: file:^.vscode/cody.json$ "command". These can be compared against the default settings.
Impact
The Cody AI VSCode extension versions >=0.10.0 and <=0.14.0 are vulnerable to Remote Code Execution under certain conditions.
An attacker in control of a malicious repository could modify the Cody configuration file
.vscode/cody.jsonand overwrite Cody commands. If a user with the extension installed opens this malicious repository and runs a Cody command such as /explain or /doc, this could allow arbitrary code execution on the user's machine.The vulnerability is rated as critical severity, but with low exploitability. It requires the user to have a malicious repository loaded and execute the overwritten command in VS Code. The issue is exploitable regardless of the user blocking code execution on a repository through VS Code Workspace Trust.
The issue was found during a regular 3rd party penetration test. We do not have evidence of open source repositories having malicious
.vscode/cody.jsonfiles to exploit this vulnerability.Patches
The issue is fixed in version 0.14.1 of the Cody VSCode extension.
Reference
PR
Workarounds
In case users can't promptly upgrade they should not open any untrusted repositories with the Cody extension loaded.
You may use the following Sourcegraph search query to find repositories overwriting Cody commands:
file:^.vscode/cody.json$ "command". These can be compared against the default settings.