Bug 1993485 (CVE-2021-32809) - CVE-2021-32809 ckeditor: clipboard feature vulnerability allowing to inject arbitrary HTML into the editor using paste functionality
Summary: CVE-2021-32809 ckeditor: clipboard feature vulnerability allowing to inject a...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2021-32809
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1993486 1993487
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-13 13:32 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-08-13 19:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-13 19:28:10 UTC
Embargoed:

Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2021-08-13 13:32:57 UTC 
ckeditor is an open source WYSIWYG HTML editor with rich content support. A potential vulnerability has been discovered in CKEditor 4 [Clipboard](https://ckeditor.com/cke4/addon/clipboard) package. The vulnerability allowed to abuse paste functionality using malformed HTML, which could result in injecting arbitrary HTML into the editor. It affects all users using the CKEditor 4 plugins listed above at version >= 4.5.2. The problem has been recognized and patched. The fix will be available in version 4.16.2.

Reference:
https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-7889-rm5j-hpgg
Comment 1 Guilherme de Almeida Suckevicz 2021-08-13 13:33:16 UTC 
Created ckeditor tracking bugs for this issue:

Affects: epel-7 [bug 1993487]
Affects: fedora-all [bug 1993486]
Comment 2 Product Security DevOps Team 2021-08-13 19:28:10 UTC 
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
Note You need to log in before you can comment on or make changes to this bug.