Smart Universal Printing DriverApplication · Hp

CVE-2024-9419

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-30
Fix available
A fix is available. Upgrade to 4.07.1.3204 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Client / Server PCs with the HP Smart Universal Printing Driver installed are potentially vulnerable to Remote Code Execution and/or Elevation of Privilege. A client using the HP Smart Universal Printing Driver that sends a print job comprised of a malicious XPS file could potentially lead to Remote Code Execution and/or Elevation of Privilege on the PC.

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 · moderate confidence

The HP Smart Universal Printing Driver contains a vulnerability where maliciously crafted XPS print job files can trigger memory corruption leading to remote code execution or elevation of privilege on affected client/server systems. The attack requires a user to send a crafted XPS file through the driver, making it a client-side code execution flaw.

MitigationUpdate the HP Smart Universal Printing Driver to the patched version provided by HP. Until patched, avoid processing untrusted or unknown XPS documents through the driver.

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
Smart Universal Printing DriverApplication
Affected:< 4.07.1.3204

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate HP Smart Universal Printing Driver
    Open Windows Print Management (printmanagement.msc) or Device Manager, expand Print queues, look for 'HP Smart Universal Printing Driver' entry
    Affected if The driver is present in the system
  2. Retrieve driver version
    Right-click the HP Smart Universal Printing Driver in Print Management, select Properties, navigate to the Driver tab to view the version number
    Affected if Version listed is lower than 4.07.1.3204
  3. Alternative version check via PowerShell
    Run Get-PrinterDriver -Name 'HP Smart Universal Printing Driver*' | Select-Object Name, Version in PowerShell (requires PrintManagement module)
    Affected if Version returned is blank (driver not found) or shows a version below 4.07.1.3204
  4. Inspect driver files directly
    Locate the driver path in the Driver tab of Print Management, then right-click the .dll file (typically hpuduxps.dll or similar), select Properties, check the File Version
    Affected if The file version displayed is below 4.07.1.3204

You are affected if the HP Smart Universal Printing Driver is installed with any version lower than 4.07.1.3204 and the system processes XPS print job files through this driver.

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
Upgrade available Upgrade to 4.07.1.3204 or later
Fixed in 4.07.1.3204
Interim mitigation

Update the HP Smart Universal Printing Driver to the patched version provided by HP. Until patched, avoid processing untrusted or unknown XPS documents through the driver.

Recommended fix High confidence

HP Smart Universal Printing Driver version 4.07.1.3204 or later

  1. Identify all systems with HP Smart Universal Printing Driver installed
  2. Navigate to HP support website (support.hp.com) and locate the HP Smart Universal Printing Driver download page
  3. Download HP Smart Universal Printing Driver version 4.07.1.3204 or later
  4. Uninstall the current vulnerable version or perform an in-place upgrade to version 4.07.1.3204
  5. Restart the print spooler service if required after installation
  6. Verify the installed version is 4.07.1.3204 or higher using the driver properties

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

Fix this in Smart Universal Printing Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-9419 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