# CVE-2022-28790: Auth bypass in Link to Windows Service

> An attacker can lock the device by exploiting improper authentication in the Link to Windows Service, requiring an upgrade to the patched version.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3q98-gw9r-j8rr

## What is CVE-2022-28790?

CVE-2022-28790 is a medium-severity authentication bypass vulnerability in Samsung Mobile Link to Windows Service, published on 3 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper authentication in Link to Windows Service prior to version 2.3.04.1 allows attacker to lock the device. The patch adds proper caller signature check logic.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Samsung Link to Windows Service.

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

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

## Is CVE-2022-28790 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28790 is a medium-severity authentication bypass vulnerability in Samsung Mobile Link to Windows Service, published on 3 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-28790 in the wild and no public exploit code.

Affected product: Samsung Mobile Link to Windows Service. 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-28790/ (Markdown: https://insights.sbomify.com/CVE-2022-28790/index.md)
```

## Sources

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

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