# CVE-2022-0915: Logitech Sync desktop application prior to 2.4.574 - TOCTOU during installation leads to privelege escalation

> A TOCTOU race condition in Logitech Sync allows attackers to escalate privileges to system user during installation.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **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:** No
- **Published:** 12 Apr 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-gjm2-49fm-q537

## What is CVE-2022-0915?

CVE-2022-0915 is a medium-severity vulnerability in Logitech Sync, published on 12 Apr 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

There is a Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability in Logitech Sync for Windows prior to 2.4.574. Successful exploitation of these vulnerabilities may escalate the permission to the system user.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 1 product.


Products: Logitech Sync.

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

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

## Is CVE-2022-0915 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0915 is a medium-severity vulnerability in Logitech Sync, published on 12 Apr 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-0915 in the wild and no public exploit code.

Affected product: Logitech Sync. 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-0915/ (Markdown: https://insights.sbomify.com/CVE-2022-0915/index.md)
```

## Sources

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

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