Nextcloud End-to-End Encryption up to 1.5.2/1.6.2/1.7.0 Folder Lock resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Nextcloud End-to-End Encryption up to 1.5.2/1.6.2/1.7.0 and classified as problematic. Impacted is an unknown function of the component Folder Lock Handler. Performing a manipulation results in resource consumption. This vulnerability is reported as CVE-2021-22906. No exploit exists. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in Nextcloud End-to-End Encryption up to 1.5.2/1.6.2/1.7.0 (Cloud Software). This affects an unknown part of the component Folder Lock Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability.
The weakness was disclosed 06/12/2021. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2021-22906. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 1.5.3, 1.6.3 or 1.7.1 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 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: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: End-to-End Encryption 1.5.3/1.6.3/1.7.1
Timeline
01/06/2021 🔍06/12/2021 🔍
06/12/2021 🔍
06/14/2021 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2021-22906 (🔍)
GCVE (CVE): GCVE-0-2021-22906
GCVE (VulDB): GCVE-100-176907
Entry
Created: 06/12/2021 07:09Updated: 06/14/2021 08:39
Changes: 06/12/2021 07:09 (39), 06/14/2021 08:39 (5)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.