dbcve.org
Universal Print DriverApplication · Samsung

CVE-2024-5760

HIGH · 7.8 CVSS v3.1 Published 2024-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

The Samsung Universal Print Driver for Windows contains a privilege escalation vulnerability that allows an attacker to gain elevated privileges and create a reverse shell. This affects printing products manufactured or released before 2018.

MitigationIdentify and inventory all affected Samsung print drivers in the environment, prioritize patching to latest versions, and implement least-privilege access controls for systems with older print drivers. Consider compensating controls such as network segmentation if patches are unavailable.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Universal Print DriverApplication
Affected:= 3.00.16.0101

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Samsung Universal Print Driver is installed
    Open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for entries containing 'Samsung Universal Print Driver'
    Affected if No Samsung Universal Print Driver is found in the installed programs list, then not affected
  2. Identify the installed Samsung Universal Print Driver version
    In Programs and Features, locate the Samsung Universal Print Driver entry and note the version number displayed, or query the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Samsung print driver entries
    Affected if The displayed version number equals exactly 3.00.16.0101
  3. Verify the driver file version
    Locate the Samsung print driver files (typically in C:\Windows\System32\spool\drivers\x64\ or the program's installation directory, often under C:\Program Files\Samsung\), right-click the main executable or DLL and select Properties > Details to view the File Version
    Affected if The file version shown in the Details tab is 3.00.16.0101

The environment is affected if Samsung Universal Print Driver version 3.00.16.0101 is installed on a Windows system, particularly on devices manufactured or released before 2018.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Identify and inventory all affected Samsung print drivers in the environment, prioritize patching to latest versions, and implement least-privilege access controls for systems with older print drivers. Consider compensating controls such as network segmentation if patches are unavailable.

Recommended fix Moderate confidence

Latest Samsung Universal Print Driver for Windows (newer than 3.00.16.0101) from HP support.hp.com

  1. 1. Visit HP Support website (support.hp.com) and search for Samsung Universal Print Driver
  2. 2. Download the latest version of the Samsung Universal Print Driver for Windows
  3. 3. Uninstall the current driver version 3.00.16.0101 from Windows Control Panel > Programs and Features
  4. 4. Install the latest available driver version from HP
  5. 5. Restart the Windows system after installation
  6. 6. Verify the installed driver version matches the latest available version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Universal Print Driver Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5760 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data