2021-32748 | Nextcloud Richdocuments WOPI authorization

CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.4 $0-$5k 0.15

A vulnerability classified as critical has been found in Nextcloud Richdocuments up to 3.8.2/4.1.x (Cloud Software). Affected is an unknown code block of the component WOPI. The manipulation with an unknown input leads to a privilege escalation vulnerability. CWE is classifying the issue as CWE-862. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Nextcloud Richdocuments in an open source self hosted online office. Nextcloud uses the WOPI (“Web Application Open Platform Interface”) protocol to communicate with the Collabora Editor, the communication between these two services was not protected by a credentials or IP check. Whilst this does not result in gaining access to data that the user has not yet access to, it can result in a bypass of any enforced watermark on documents as described on the [Nextcloud Virtual Data Room](https://nextcloud.com/virtual-data-room/) website and [our documentation](https://portal.nextcloud.com/article/nextcloud-and-virtual-data-room-configuration-59.html). The Nextcloud Richdocuments releases 3.8.3 and 4.2.0 add an additional admin settings for an allowlist of IP addresses that can access the WOPI API. We recommend upgrading and configuring the allowlist to a list of Collabora servers. There is no known workaround. Note that this primarily results a bypass of any configured watermark or download protection using File Access Control. If you do not require or rely on these as a security feature no immediate action is required on your end.

The weakness was published 07/28/2021. The advisory is available at github.com. This vulnerability is traded as CVE-2021-32748 since 05/12/2021. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn’t require any form of authentication. The technical details are unknown and an exploit is not available.

Upgrading to version 3.8.3 or 4.2.0 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.




VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

🔍 🔍 🔍 🔍 🔍 🔍
🔍 🔍 🔍 🔍 🔍 🔍
🔍 🔍 🔍 🔍 🔍 🔍
Vector Complexity Authentication Confidentiality Integrity Availability
unlock unlock unlock unlock unlock unlock
unlock unlock unlock unlock unlock unlock
unlock unlock unlock unlock unlock unlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Class: Privilege escalation
CWE: CWE-862
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

Price Prediction: 🔍
Current Price Estimation: 🔒

0-Day unlock unlock unlock unlock
Today unlock unlock unlock unlock

Threat Intelligenceinfoedit

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Richdocuments 3.8.3/4.2.0
Patch: github.com

05/12/2021 CVE assigned
07/28/2021 +77 days Advisory disclosed
07/28/2021 +0 days VulDB entry created
08/05/2021 +8 days VulDB last updateAdvisory: github.com
Status: Confirmed
Confirmation: 🔒

CVE: CVE-2021-32748 (🔒)

Created: 07/28/2021 07:00
Updated: 08/05/2021 14:44
Changes: (1) source_cve_cna
Complete: 🔍

Download the whitepaper to learn more about our service!

Source link