Open VSX Registry does not sanitize SVG files uploaded as extension icons prior to storage, and serves them with Content-Type: image/svg+xml without security headers such as Content-Security-Policy or Content-Disposition: attachment. This allows an attacker to publish an extension with a malicious SVG icon and achieve stored cross-site scripting (XSS) when a user navigates directly to the icon URL. On deployments using local storage, script execution occurs within the Open VSX application origin, enabling session hijacking, authentication token theft, and unauthorized extension publishing. On deployments backed by external storage (such as open-vsx.org with an S3-backed CDN), execution is confined to the storage origin, reducing impact but still permitting phishing attacks and credential harvesting through attacker-crafted pages.
oryginał ENCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:NEclipse Open Vsx
APPEclipse0.1.0 – 0.34.1 (bez)
Powiązane podatności
A vulnerability in the Eclipse Open VSX Registry’s automated publishing system could have allowed unauthorized...
In OpenVSX version v0.9.0 to v0.20.0, the /user/namespace/{namespace}/details API allows a user to edit all ...
An authenticated Remote Code Execution (RCE) vulnerability was identified in GlassFish's Administration Consol...
A critical Remote Code Execution (RCE) vulnerability was identified in the server-side template rendering mech...
Path Traversal w Eclipse OpenMQ umożliwia odczyt plików i potencjalny RCE