First published: Fri Feb 07 2025(Updated: )
An issue has been discovered in the gitlab-web-ide-vscode-fork component distributed over CDN affecting all versions prior to 1.89.1-1.0.0-dev-20241118094343and used by all versions of GitLab CE/EE starting from 15.11 prior to 17.3 and which also temporarily affected versions 17.4, 17.5 and 17.6, where a XSS attack was possible when loading .ipynb files in the web IDE
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | <1.89.1-1.0.0-dev-20241118094343 | |
GitLab Community Edition | >=15.11<17.3>=17.4<17.7 |
Upgrade to GitLab version 17.3, 17.4, 17.5, 17.6 or later.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-10383 is classified as a high severity vulnerability due to its potential impact on affected versions of GitLab and the gitlab-web-ide-vscode-fork component.
To fix CVE-2024-10383, upgrade the gitlab-web-ide-vscode-fork component to version 1.89.1 or later, and ensure that GitLab CE/EE is updated to a version greater than 17.3.
CVE-2024-10383 affects all versions of gitlab-web-ide-vscode-fork prior to 1.89.1-1.0.0-dev-20241118094343 and all GitLab CE/EE versions from 15.11 up to, but not including, 17.3.
CVE-2024-10383 may expose sensitive user data and compromise the security posture of GitLab users utilizing the affected components.
The components affected by CVE-2024-10383 include gitlab-web-ide-vscode-fork and the broader GitLab CE/EE application.