Skip to content
Fencer Intel
medium 6.9

CVE-2023-28999 json

Nextcloud: Lack of authenticity of metadata keys allows a malicious server to gain access to E2EE folders

published 3y ago modified 2mo ago also BIT-nextcloud-2023-28999 , EUVD-2023-32617 , GHSA-8875-wxww-3rr8

cvss
6.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

Nextcloud is an open-source productivity platform. In Nextcloud Desktop client 3.0.0 until 3.8.0, Nextcloud Android app 3.13.0 until 3.25.0, and Nextcloud iOS app 3.0.5 until 4.8.0, a malicious server administrator can gain full access to an end-to-end encrypted folder. They can decrypt files, recover the folder structure and add new files.​ This issue is fixed in Nextcloud Desktop 3.8.0, Nextcloud Android 3.25.0, and Nextcloud iOS 4.8.0. No known workarounds are available.

Patch / fix

  • bitnami nextcloud 4.8.0
  • nextcloud desktop 3.8.0
  • nextcloud nextcloud 3.25.0, 4.8.0
  • nextcloud-desktop Debian 14, Debian 13 3.9.0-1

debian advisories DEBIAN-CVE-2023-28999

  • nextcloud-client Alpine 3.24, Alpine 3.23, Alpine 3.22 +4 more 3.8.1-r0

alpine advisories ALPINE-CVE-2023-28999

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2023-28999 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-28999 updated cvss 4.4

nextloucd-client: malicious server administrator can gain full access to an end-to-end encrypted folder

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-15).

Exploits and checks

  • ethz.ch https://ethz.ch/content/dam/ethz/special-interest/infk/inst-infsec/appliedcrypto/education/theses/report_DanieleCoppola.pdf referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.9 CVSS:3.1/AV:P/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:L
NVD 3.1 6.4 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L
OSV 3.1 6.4 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L

Affected packages

ecosystem package affected fixed in
bitnami nextcloud
>=3.0.5, <4.8.0
4.8.0

Affected products

  • nextcloud security-advisories

Classification

Weakness
  • CWE-325 Missing Cryptographic Step
  • CWE-311 Missing Encryption of Sensitive Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.