CVE-2021-32680
Published: 12 July 2021
Summary
CVE-2021-32680 is a low-severity Insufficient Logging (CWE-778) vulnerability in Nextcloud Nextcloud Server. Its CVSS base score is 3.3 (Low).
Operationally, ranked at the 42.0th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2021-19488
Vulnerability details
Nextcloud Server is a Nextcloud package that handles data storage. In versions priot to 19.0.13, 20.0.11, and 21.0.3, Nextcloud Server audit logging functionality wasn't properly logging events for the unsetting of a share expiration date. This event is supposed to…
more
be logged. This issue is patched in versions 19.0.13, 20.0.11, and 21.0.3.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Audit policy requires defining and implementing logging of security-relevant events, directly reducing insufficient logging.
Providing proof of performed actions necessitates sufficient logging of security-relevant events with attribution details.
Retaining audit records for a defined period ensures security-relevant events remain available for after-the-fact investigations, directly mitigating the risk that attackers can hide actions due to missing or purged log data.
Directly requires generation of audit records for specified events, preventing the absence of logging that allows undetected malicious activity.
Directly implements detailed session logging to address the weakness of insufficient logging.
Provides alternate logging mechanism to maintain audit trails when primary capability fails, directly reducing insufficient logging.
Employing coordination mechanisms ensures consistent and sufficient logging practices are applied when audit information crosses organizational boundaries.
This control requires identifying, specifying, and justifying event types for logging with a focus on adequacy for post-incident investigations, directly mitigating insufficient logging.