-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Security vulnerability in [email protected] (used by VSCode & Monaco) #4692
Comments
It looks like DOMPurify was bumped here https://github.com/microsoft/vscode/pull/228773/files but not yet vendored like in this other DOMPurify bump PR - https://github.com/microsoft/vscode/pull/189368/files |
@rzhao271 Just wanted to at you as you merged in the version update for DOMPurify |
Looks like one more CVE is found now CVE-2024-47875, but still updating to [email protected] should solve an issue |
This pr will bump to the currently latest release (3.1.7): microsoft/vscode#230250 |
Closing as upstream change in VS Code has been merged |
@mjbvz thank you for fixing the issue 👍. Do you happen to know when 0.53 monaco-editor version will be released with the vulnerability fix? |
Hi, when do you plan to release the fix in the Monaco-editor? Thanks |
@aleixsuau it is tracked in #4738, no idea when it will be released unfortunately |
Reproducible in vscode.dev or in VS Code Desktop?
Reproducible in the monaco editor playground?
Monaco Editor Playground Link
No response
Monaco Editor Playground Code
No response
Reproduction Steps
No response
Actual (Problematic) Behavior
Our OWASP scan detected an issue in [email protected] CVE-2024-45801 which seems to be used by the Monaco editor (VSCode): https://github.com/microsoft/vscode/blob/main/src/vs/base/browser/dompurify/dompurify.js
Please update to [email protected] to get rid of that vulnerability.
Thanks
Expected Behavior
There should be no vulnerability issues.
Additional Context
No response
The text was updated successfully, but these errors were encountered: