# CVE-2022-41882: Nextcloud Desktop vulnerable to code injection via malicious link

> Attackers can execute arbitrary code on Windows systems by tricking users into clicking malicious nc:// links in synced files.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Nov 2022
- **Updated:** 23 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-41882, GHSA-3w86-rm38-8w63, UBUNTU-CVE-2022-41882

## What is CVE-2022-41882?

CVE-2022-41882 is a medium-severity code injection vulnerability in nextcloud security-advisories, published on 11 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Nextcloud Desktop Client is a tool to synchronize files from Nextcloud Server with your computer. In version 3.6.0, if a user received a malicious file share and has it synced locally or the virtual filesystem enabled and clicked a nc://open/ link it will open the default editor for the file type of the shared file, which on Windows can also sometimes mean that a file depending on the type, e.g. "vbs", is being executed. It is recommended that the Nextcloud Desktop client is upgraded to version 3.6.1. As a workaround, users can block the Nextcloud Desktop client 3.6.0 by setting the `minimum.supported.desktop.version` system config to `3.6.1` on the server, so new files designed to use this attack vector are not downloaded anymore. Already existing files can still be used. Another workaround would be to enforce shares to be accepted by setting the `sharing.force_share_accept` system config to `true` on the server, so new files designed to use this attack vector are not downloaded anymore. Already existing shares can still be abused.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-41882?

It affects 1 product.


Products: Nextcloud Desktop.

## How do I fix CVE-2022-41882?

Upgrade to a fixed version.

## Is CVE-2022-41882 being exploited?

There is no known exploitation of CVE-2022-41882 in the wild and no public exploit code.

## Other vulnerabilities in nextcloud security-advisories

- [CVE-2024-46958](https://insights.sbomify.com/CVE-2024-46958/): Misconfiguration in n/a (critical 9.1)
- [CVE-2020-8224](https://insights.sbomify.com/CVE-2020-8224/): Code injection in Desktop Client (high 7.8)
- [CVE-2020-8225](https://insights.sbomify.com/CVE-2020-8225/): Information disclosure in Desktop Client (high 7.5)
- [CVE-2021-37617](https://insights.sbomify.com/CVE-2021-37617/): Untrusted Search Path in Nextcloud Desktop Client (high 7.3)
- [CVE-2023-28999](https://insights.sbomify.com/CVE-2023-28999/): Nextcloud: Lack of authenticity of metadata keys allows a malicious server to gain access to E2EE folders (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41882 and fix it if it is affected.

What it is: CVE-2022-41882 is a medium-severity code injection vulnerability in nextcloud security-advisories, published on 11 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-41882 in the wild and no public exploit code.

Affected product: nextcloud security-advisories. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41882/ (Markdown: https://insights.sbomify.com/CVE-2022-41882/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41882
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41882
- OSV: https://osv.dev/vulnerability/CVE-2022-41882

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41882/
Summaries are generated and may contain mistakes; the official description above is the record.