Bug 2024960 (CVE-2021-39222) - CVE-2021-39222 nextcloud: Stored Cross-Site Scripting in Talk
Summary: CVE-2021-39222 nextcloud: Stored Cross-Site Scripting in Talk
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2021-39222
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2024962
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-19 15:18 UTC by Pedro Sampaio
Modified: 2021-11-19 15:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-19 15:51:02 UTC


Attachments (Terms of Use)

Description Pedro Sampaio 2021-11-19 15:18:16 UTC
Nextcloud is an open-source, self-hosted productivity platform. The Nextcloud Talk application was vulnerable to a stored Cross-Site Scripting (XSS) vulnerability. For exploitation, a user would need to right-click on a malicious file and open the file in a new tab. Due the strict Content-Security-Policy shipped with Nextcloud, this issue is not exploitable on modern browsers supporting Content-Security-Policy. It is recommended that the Nextcloud Talk application is upgraded to patched versions 10.0.7, 10.1.4, 11.1.2, 11.2.0 or 12.0.0. As a workaround, use a browser that has support for Content-Security-Policy.

https://github.com/nextcloud/security-advisories/security/advisories/GHSA-xhxq-f4vg-jw5g
https://hackerone.com/reports/1135481
https://github.com/nextcloud/spreed/pull/542

Comment 1 Pedro Sampaio 2021-11-19 15:19:59 UTC
Created nextcloud tracking bugs for this issue:

Affects: fedora-all [bug 2024962]

Comment 2 Product Security DevOps Team 2021-11-19 15:51:01 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.