Advisory

GHSA-42wq-rch8-6f6j

Also known as: CVE-2022-31175

Summary

CKEditor5 cross-site scripting vulnerability caused by the editor instance destroying process

Details

Affected packages
@ckeditor/ckeditor5-markdown-gfm
@ckeditor/ckeditor5-html-support
@ckeditor/ckeditor5-html-embed

Impact
A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5's packages. The vulnerability allowed to trigger a JavaScript code after fulfilling special conditions:

a) 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,
b) Initializing the editor on an element and using an element other than <textarea> as a base,
c) Destroying the editor instance.

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.

Patches
The problem has been recognized and patched. The fix will be available in version 35.0.1.

For more information
Email us at [[email protected]](mailto:[email protected]) if you have any questions or comments about this advisory.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2022-08-06 09:40 UTC
Modified
2023-11-08 04:09 UTC

Affected packages and fixes

@ckeditor/ckeditor5-markdown-gfm

npm · All systems

Affected

  • introduced 0, fixed 35.0.1 (semver)

Fixed versions

35.0.1

Fix

@ckeditor/ckeditor5-html-support

npm · All systems

Affected

  • introduced 0, fixed 35.0.1 (semver)

Fixed versions

35.0.1

Fix

@ckeditor/ckeditor5-html-embed

npm · All systems

Affected

  • introduced 0, fixed 35.0.1 (semver)

Fixed versions

35.0.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences