# CVE-2024-5760: Privilege escalation in Samsung Universal Print Driver

> Attackers can escalate privileges and create a reverse shell in older Samsung Universal Print Drivers for Windows.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2024
- **Updated:** 11 Sep 2024
- **Also known as:** GHSA-94f8-mx94-9x98

## What is CVE-2024-5760?

CVE-2024-5760 is a high-severity vulnerability in HP Inc. Samsung Universal Print Driver, published on 11 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Samsung Universal Print Driver for Windows is potentially vulnerable to escalation of privilege allowing the creation of a reverse shell in the tool. This is only applicable for products in the application released or manufactured before 2018.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-5760?

It affects 1 product.


Products: Samsung Universal Print Driver.

## How do I fix CVE-2024-5760?

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

## Is CVE-2024-5760 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5760 and fix it if it is affected.

What it is: CVE-2024-5760 is a high-severity vulnerability in HP Inc. Samsung Universal Print Driver, published on 11 Sep 2024. 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-2024-5760 in the wild and no public exploit code.

Affected product: HP Inc. Samsung Universal Print Driver. 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-2024-5760/ (Markdown: https://insights.sbomify.com/CVE-2024-5760/index.md)
```

## Sources

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

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