CVE-2025-53097
BaseFortify
Publication date: 2025-06-27
Last updated on: 2025-09-15
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| roocode | roo_code | to 3.20.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Roo Code versions prior to 3.20.3 involves the `search_files` tool not respecting the setting that disables reading files outside the VS Code workspace. An attacker who can inject prompts into the agent could exploit this to read sensitive files outside the workspace and write that information to a JSON schema. Since schema fetching is enabled by default, this writing action could trigger a network request without user consent, potentially leaking sensitive data. The issue was fixed in version 3.20.3 by enforcing the workspace restriction.
How can this vulnerability impact me? :
If exploited, this vulnerability could allow an attacker to read sensitive files outside the intended workspace and exfiltrate that information via network requests triggered by writing to a JSON schema. This could lead to unauthorized disclosure of sensitive data. However, exploitation requires the attacker to already be able to submit prompts to the Roo Code agent, and users can mitigate risk by disabling schema fetching or updating to version 3.20.3 or later.
What immediate steps should I take to mitigate this vulnerability?
Upgrade Roo Code to version 3.20.3 or later, as this version fixes the issue where the `search_files` tool did not respect the setting to limit file reads to the VS Code workspace. Additionally, consider disabling schema fetching in VS Code to prevent automatic network requests triggered by writing to the JSON schema.