Cyber Resilience

CVE-2022-39329

Low

Published: 27 October 2022

Published
27 October 2022
Modified
21 November 2024
KEV Added
Patch
CVSS Score v3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
EPSS Score 0.0026 50.0th percentile
Risk Priority 7 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2022-39329 is a low-severity Improper Access Control (CWE-284) vulnerability in Nextcloud Nextcloud Enterprise Server. Its CVSS base score is 3.5 (Low).

Operationally, ranked in the top 50.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability details

Nextcloud Server is the file server software for Nextcloud, a self-hosted productivity platform. Nextcloud Server and Nextcloud Enterprise Server prior to versions 23.0.9 and 24.0.5 are vulnerable to exposure of information that cannot be controlled by administrators without direct database…

more

access. Versions 23.0.9 and 24.0.5 contains patches for this issue. No known workarounds are available.

CWE(s)

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

Affected Assets

nextcloud
nextcloud enterprise server
≤ 23.0.9 · 24.0.0 — 24.0.5
nextcloud
nextcloud server
≤ 23.0.9 · 24.0.0 — 24.0.5

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.

The access control policy and procedures directly mandate and enforce proper access control mechanisms across the organization.

Supervision and review of access control activities directly detects and remediates improper access configurations or usages.

Explicitly identifying and documenting actions permitted without identification or authentication enforces proper access control boundaries by defining justified exceptions.

Associating and retaining security attributes with data directly supports enforcement of access control decisions across storage, processing, and transmission.

Requiring prior authorization for each remote access type prevents improper access control over remote connections.

Requiring authorization of wireless access before allowing connections enforces proper access control for this access method.

Requiring authorization and configuration controls for mobile device connections directly enforces access control and prevents unauthorized devices from reaching organizational systems.

Defining account types, requiring approvals for creation, specifying authorizations, monitoring usage, and reviewing accounts directly prevents improper access control by ensuring only authorized accounts exist and are used.

References