CVE-2022-31175 Cross-site scripting caused by the editor instance destroying process in ckeditor5
Cross-site scripting in CKEditor 5 allows JavaScript execution when destroying and reinitializing the editor with unsafe markup enabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2022-31175?
CVE-2022-31175 is a medium-severity cross-site scripting vulnerability in ckeditor5, published on 3 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
CKEditor 5 is a JavaScript rich text editor. A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5's packages in versions prior to 35.0.1. The vulnerability allowed to trigger a JavaScript code after fulfilling special conditions. The affected packages are `@ckeditor/ckeditor5-markdown-gfm`, `@ckeditor/ckeditor5-html-support`, and `@ckeditor/ckeditor5-html-embed`. The specific conditions are 1) Using one of the affected packages. In case of `ckeditor5-html-support` and `ckeditor5-html-embed`, additionally, it was required to use a configuration that allows unsafe markup inside the editor. 2) Destroying the editor instance and 3) Initializing the editor on an element and using an element other than `<textarea>` as a base. The root cause of the issue was a mechanism responsible for updating the source element with the markup coming from the CKEditor 5 data pipeline after destroying the editor. This vulnerability might affect a small percent of integrators that depend on dynamic editor initialization/destroy and use Markdown, General HTML Support or HTML embed features. The problem has been recognized and patched. The fix is available in version 35.0.1. There are no known workarounds for this issue.
Weakness: CWE-79
Which versions are affected by CVE-2022-31175?
6 open source packages ship an affected version, including @ckeditor/ckeditor5-html-embed, @ckeditor/ckeditor5-html-support and @ckeditor/ckeditor5-markdown-gfm. It affects 3 products.
| Package | Affected | Fixed in |
|---|---|---|
@ckeditor/ckeditor5-html-embed npm | All versions | 35.0.1 |
@ckeditor/ckeditor5-html-embed npm | All versions | 35.0.1 |
@ckeditor/ckeditor5-html-support npm | All versions | 35.0.1 |
@ckeditor/ckeditor5-html-support npm | All versions | 35.0.1 |
@ckeditor/ckeditor5-markdown-gfm npm | All versions | 35.0.1 |
@ckeditor/ckeditor5-markdown-gfm npm | All versions | 35.0.1 |
Products include Ckeditor Ckeditor5-Html-Embed, Ckeditor Ckeditor5-Html-Support, Ckeditor Ckeditor5-Markdown-Gfm.
How do I fix CVE-2022-31175?
Upgrade @ckeditor/ckeditor5-html-embed to 35.0.1 or later.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2022-31175 being exploited?
There is no known exploitation of CVE-2022-31175 in the wild and no public exploit code.
Sources
Also known as GHSA-42wq-rch8-6f6j, UBUNTU-CVE-2022-31175.