dbcve.org
Virtual Appliance ApplicationApplication · Vasion

CVE-2025-34193

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 25.1.102 and Application versions prior to 25.1.1413 include Windows client components (PrinterInstallerClientInterface.exe, PrinterInstallerClient.exe, PrinterInstallerClientLauncher.exe) that lack modern compile-time and runtime exploit mitigations and rely on outdated runtimes. These binaries are built as 32-bit, without Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), Control Flow Guard (CFG), or stack-protection, and they incorporate legacy technologies (Pascal/Delphi and Python 2) which are no longer commonly maintained. Several of these processes run with elevated privileges (NT AUTHORITY\SYSTEM for PrinterInstallerClient.exe and PrinterInstallerClientLauncher.exe), and the client automatically downloads and installs printer drivers. The absence of modern memory safety mitigations and the use of unmaintained runtimes substantially increase the risk that memory-corruption or other exploit primitives — for example from crafted driver content or maliciously crafted inputs — can be turned into remote or local code execution and privilege escalation to SYSTEM. This vulnerability has been confirmed to be remediated, but it is unclear as to when the patch was introduced.

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

Vasion Print client binaries (PrinterInstallerClientInterface.exe, PrinterInstallerClient.exe, PrinterInstallerClientLauncher.exe) lack critical memory protection mitigations (DEP, ASLR, CFG, stack canaries) and are built as 32-bit binaries using deprecated Pascal/Delphi and Python 2 technologies. Multiple processes run as NT AUTHORITY\SYSTEM and automatically download/install printer drivers, enabling memory corruption exploits to achieve remote code execution and privilege escalation.

MitigationUpgrade Vasion Print Virtual Appliance Host to version 25.1.102 or later, and Application to version 25.1.1413 or later. Prioritize systems with direct internet exposure given the CVSS 9.8 critical rating.

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
Virtual Appliance ApplicationApplication
Affected:all versions
Virtual Appliance HostApplication
Affected:all versions

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 Vasion Print client binaries
    Search for PrinterInstallerClientInterface.exe, PrinterInstallerClient.exe, and PrinterInstallerClientLauncher.exe in common installation directories (C:\Program Files\Vasion, C:\Program Files (x86)\Vasion) or use 'Get-ChildItem -Path C:\ -Recurse -Filter PrinterInstallerClient*.exe -ErrorAction SilentlyContinue' to find them across the system
    Affected if Any of the three named executables are found on the system, indicating Vasion Print client is installed
  2. Determine installed Vasion Virtual Appliance Host version
    Right-click each PrinterInstallerClient binary, select Properties, and check the Details tab for File Version or Product Version. Alternatively, check the Windows Programs and Features list for 'Vasion Virtual Appliance Host' entry and its installed version
    Affected if The Host version is present and is below 25.1.102 (or version is not shown/unknown, as all versions are affected)
  3. Determine installed Vasion Virtual Appliance Application version
    Check Windows Programs and Features for 'Vasion Virtual Appliance Application' entry, or look for version information in the application's installation directory (commonly under C:\Program Files\Vasion\Virtual Appliance Application or similar)
    Affected if The Application version is present and is below 25.1.1413 (or version is not shown/unknown, as all versions are affected)
  4. Verify binary architecture (32-bit check)
    Use 'dumpbin /headers PrinterInstallerClient.exe' from Visual Studio tools or 7-Zip right-click to check 'Machine' field in PE headers - look for 'x86' (32-bit) versus 'x64' (64-bit)
    Affected if Binaries are compiled as 32-bit (x86), which is one of the weaknesses enabling the exploitation path

If Vasion Virtual Appliance Host or Application is installed with versions below 25.1.102 or 25.1.1413 respectively (or version cannot be determined), the environment is affected by this vulnerability.

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

Upgrade Vasion Print Virtual Appliance Host to version 25.1.102 or later, and Application to version 25.1.1413 or later. Prioritize systems with direct internet exposure given the CVSS 9.8 critical rating.

Recommended fix Moderate confidence

Virtual Appliance Host version 25.1.102 or later; Virtual Appliance Application version 25.1.1413 or later (prefer latest stable release)

  1. 1. Identify the currently installed Virtual Appliance Host and Application versions in your Vasion Print environment
  2. 2. For Virtual Appliance Host: Upgrade to version 25.1.102 or later
  3. 3. For Virtual Appliance Application: Upgrade to version 25.1.1413 or later
  4. 4. If available, upgrade to the most recent stable release of both components to ensure all security mitigations are applied
  5. 5. After upgrade, verify that the PrinterInstallerClient.exe, PrinterInstallerClientLauncher.exe, and PrinterInstallerClientInterface.exe processes now run with appropriate mitigations (confirm via vendor release notes)
  6. 6. Test printer driver deployment functionality to ensure the upgrade did not break existing printing workflows
Caveat Review Vasion Print release notes for any changes to printer driver deployment behavior or deprecated features between current and target versions

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

Fix this in Virtual Appliance Application Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34193 — 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-2025-34193 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