Prototype Pollution@theia/core is a the main extension for all Theia-based applications, and provides the main framework for all dependent extensions.
Affected versions of this package are vulnerable to Prototype Pollution via the PreferenceUtils.merge function in PreferenceUtils within preference resolution. An attacker can pollute Object.prototype and alter application logic by supplying crafted workspace preference JSON such as .theia/settings.json or .vscode/settings.json that is merged when the user opens the workspace. Because PreferenceServiceImpl.doResolve invokes this merge path across default, user, workspace, and folder scopes, a malicious nested __proto__, constructor, or prototype key in preference data can affect objects throughout the Theia process, causing incorrect behavior for the user and potentially impacting other features that rely on plain object properties.
How to fix Prototype Pollution? Upgrade @theia/core to version 1.74.0 or higher.
| |
Server-side Request Forgery (SSRF)@theia/core is a the main extension for all Theia-based applications, and provides the main framework for all dependent extensions.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the request-service process. An attacker can access sensitive internal resources by sending crafted URLs to the backend, which then performs server-side HTTP requests and returns the responses. This can expose internal administrative endpoints, cloud instance metadata services, and other resources not intended to be accessible from the client. This is only exploitable if the service connection is reachable by untrusted users, such as in multi-tenant or publicly accessible deployments.
How to fix Server-side Request Forgery (SSRF)? Upgrade @theia/core to version 1.73.0 or higher.
| |
Missing Origin Validation in WebSockets@theia/core is a the main extension for all Theia-based applications, and provides the main framework for all dependent extensions.
Affected versions of this package are vulnerable to Missing Origin Validation in WebSockets via the shell-terminal and terminals/:id WebSocket endpoints when origin validation is bypassed due to missing or manipulated headers. An attacker can execute arbitrary operating system commands and access their output by enticing a user to visit a malicious web page while a vulnerable instance is running.
How to fix Missing Origin Validation in WebSockets? Upgrade @theia/core to version 1.73.0 or higher.
| |