Bug 1981818 (CVE-2021-32679) - CVE-2021-32679 nextcloud: filenames not escaped by default in controllers using DownloadResponse
Summary: CVE-2021-32679 nextcloud: filenames not escaped by default in controllers usi...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2021-32679
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: 1981819
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-13 13:40 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-07-13 21:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-13 21:55:06 UTC


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2021-07-13 13:40:01 UTC
Nextcloud Server is a Nextcloud package that handles data storage. In versions prior to 19.0.13, 20.0.11, and 21.0.3, filenames where not escaped by default in controllers using `DownloadResponse`. When a user-supplied filename was passed unsanitized into a `DownloadResponse`, this could be used to trick users into downloading malicious files with a benign file extension. This would show in UI behaviours where Nextcloud applications would display a benign file extension (e.g. JPEG), but the file will actually be downloaded with an executable file extension. The vulnerability is patched in versions 19.0.13, 20.0.11, and 21.0.3. Administrators of Nextcloud instances do not have a workaround available, but developers of Nextcloud apps may manually escape the file name before passing it into `DownloadResponse`.

Reference:
https://github.com/nextcloud/security-advisories/security/advisories/GHSA-3hjp-26x8-mhf6

Comment 1 Guilherme de Almeida Suckevicz 2021-07-13 13:40:34 UTC
Created nextcloud tracking bugs for this issue:

Affects: fedora-all [bug 1981819]

Comment 2 Product Security DevOps Team 2021-07-13 21:55:06 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.