Summary
There was an issue where the Roo Code agent's search_files tool did not respect the setting to disable reads outside of the VS Code workspace. This means that an attacker who was able to inject a prompt into the agent could potentially read a sensitive file and then write the information to a JSON schema.
Users have the option to disable schema fetching in VS Code, but the feature is enabled by default. For users with this feature enabled, writing to the schema would trigger a network request without the user having a chance to deny.
Impact
This issue is of moderate severity, since it requires the attacker to already be able to submit prompts to the agent.
Remediation
We fixed the issue where search_files did not respect the setting to limit it to the workspace. This reduces the scope of the damage if an attacker is able to take control of the agent through prompt injection or another vector.
MaccariTA Reporter
Summary
There was an issue where the Roo Code agent's
search_filestool did not respect the setting to disable reads outside of the VS Code workspace. This means that an attacker who was able to inject a prompt into the agent could potentially read a sensitive file and then write the information to a JSON schema.Users have the option to disable schema fetching in VS Code, but the feature is enabled by default. For users with this feature enabled, writing to the schema would trigger a network request without the user having a chance to deny.
Impact
This issue is of moderate severity, since it requires the attacker to already be able to submit prompts to the agent.
Remediation
We fixed the issue where
search_filesdid not respect the setting to limit it to the workspace. This reduces the scope of the damage if an attacker is able to take control of the agent through prompt injection or another vector.