# CVE-2022-41796: Privilege escalation in Content Transfer (for Windows)

> Attackers can gain privileges via a Trojan horse DLL in the Sony Content Transfer installer due to an untrusted search path vulnerability.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** GHSA-3fx6-2v2x-qmr9

## What is CVE-2022-41796?

CVE-2022-41796 is a high-severity vulnerability in Sony Corporation Content Transfer (for Windows), published on 24 Oct 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

Untrusted search path vulnerability in the installer of Content Transfer (for Windows) Ver.1.3 and prior allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Sony Content Transfer.

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

No fix has been published for CVE-2022-41796 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41796 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41796 is a high-severity vulnerability in Sony Corporation Content Transfer (for Windows), published on 24 Oct 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-41796 in the wild and no public exploit code.

Affected product: Sony Corporation Content Transfer (for Windows). 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-41796/ (Markdown: https://insights.sbomify.com/CVE-2022-41796/index.md)
```

## Sources

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

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