Nextcloud Enterprise ServerApplication · Nextcloud

CVE-2022-39364

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-27
Fix available
A fix is available. Upgrade to 22.2.10.5 / 23.0.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Nextcloud Server is the file server software for Nextcloud, a self-hosted productivity platform. In Nextcloud Server prior to versions 23.0.9 and 24.0.5 and Nextcloud Enterprise Server prior to versions 22.2.10.5, 23.0.9, and 24.0.5 an attacker reading `nextcloud.log` may gain knowledge of credentials to connect to a SharePoint service. Nextcloud Server versions 23.0.9 and 24.0.5 and Nextcloud Enterprise Server versions 22.2.10.5, 23.0.9, and 24.0.5 contain a patch for this issue. As a workaround, set `zend.exception_ignore_args = On` as an option in `php.ini`.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nextcloud Enterprise ServerApplication
Affected:< 22.2.10.5>= 23.0.0, < 23.0.9>= 24.0.0, < 24.0.5
Nextcloud ServerApplication
Affected:< 23.0.9>= 24.0.0, < 24.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 22.2.10.5 / 23.0.9 / 24.0.5 or later
Fixed in 22.2.10.523.0.924.0.5
Vendor patch github.com →
Recommended fix High confidence

Nextcloud Server 23.0.9 or 24.0.5; Nextcloud Enterprise Server 22.2.10.5, 23.0.9, or 24.0.5

  1. 1. Back up your Nextcloud instance (database, data directory, and config.php)
  2. 2. Put your Nextcloud server into maintenance mode: `occ maintenance:mode --on`
  3. 3. Update your Nextcloud installation using your package manager or by downloading the new version from https://nextcloud.com/install/
  4. 4. If using a package manager (e.g., apt, yum), run: `apt update && apt install nextcloud-server` or equivalent for your system
  5. 5. After update completes, run database migrations: `occ upgrade`
  6. 6. Clear the application cache: `occ maintenance:repair`
  7. 7. Disable maintenance mode: `occ maintenance:mode --off`
  8. 8. Verify the update was successful by checking the Nextcloud admin panel and that the version matches 23.0.9 or 24.0.5
Caveat Patch releases typically have minimal breaking changes; however, test in staging first especially when crossing major version boundaries

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39364 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data