CVE-2025-34195
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 · uneditedVasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 1.0.735 and Application prior to 20.0.1330 (Windows client deployments) contain a remote code execution vulnerability during driver installation caused by unquoted program paths. The PrinterInstallerClient driver-installation component launches programs using an unquoted path under "C:\Program Files (x86)\Printer Properties Pro\Printer Installer". Because the path is unquoted, the operating system may execute a program located at a short-path location such as C:\Program.exe before the intended binaries in the quoted path. If an attacker can place or cause a program to exist at that location, it will be executed with the privileges of the installer process (which may be elevated), enabling arbitrary code execution and potential privilege escalation. This weakness can be used to achieve remote code execution and full compromise of affected Windows endpoints. This vulnerability has been identified by the vendor as: V-2022-006 — Driver Upload Security.
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 confidenceVasion Print Virtual Appliance and Windows client deployments contain an unquoted path vulnerability in the PrinterInstallerClient driver-installation component. The path 'C:\Program Files (x86)\Printer Properties Pro\Printer Installer' lacks quotes, allowing Windows to execute a malicious program at a short-path location (e.g., C:\Program.exe) before the intended binary, achieving arbitrary code execution with elevated privileges during driver installation.
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< 20.0.1330< 1.0.735CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify PrinterInstallerClient service existsOpen Command Prompt as Administrator and run: sc query PrinterInstallerClientAffected if The service 'PrinterInstallerClient' is found in the output, indicating the vulnerable component is installed
-
Inspect service binary path for unquoted spacesRun: sc qc PrinterInstallerClient and examine the BINARY_PATH_NAME fieldAffected if The path contains spaces and is not enclosed in quotes (e.g., shows C:\Program Files (x86)\Printer Properties Pro\Printer Installer\... without quotes)
-
Check for executable files in parent directoriesList contents of C:\ to verify if Program.exe exists: dir C:\Program.exeAffected if A file named Program.exe exists in C:\, which could be maliciously executed due to the unquoted path vulnerability
-
Determine installed Vasion/PrinterLogic versionCheck installed software version via registry: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\PrinterLogic" /v DisplayVersion or check Add/Remove ProgramsAffected if The installed version is below 20.0.1330 for Windows client, or Virtual Appliance version is below 1.0.735
-
Verify Virtual Appliance version (if applicable)Access Virtual Appliance admin interface and navigate to System Info or run: vamctl get versionAffected if The Virtual Appliance Host version is below 1.0.735 or Application version is below 20.0.1330
A system is affected if the PrinterInstallerClient service is installed with an unquoted path containing spaces and the installed version is below 20.0.1330 (Windows) or the Virtual Appliance is below version 1.0.735.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.73520.0.1330
Upgrade Vasion Print Virtual Appliance Host to version 1.0.735+ and Application to version 20.0.1330+ for Windows client deployments. Alternatively, implement path quoting in the installer configuration or deploy application controls to prevent execution from short-path locations.
Virtual Appliance Host 1.0.735 and Virtual Appliance Application 20.0.1330
- Identify which Virtual Appliance component is installed (Host and/or Application) using the PrinterLogic/Vasion Print admin console
- Navigate to help.printerlogic.com or the vendor's software download portal
- Download Virtual Appliance Host version 1.0.735 or later
- Download Virtual Appliance Application version 20.0.1330 or later
- Apply updates during a maintenance window following vendor upgrade instructions
- Verify the installed versions post-upgrade to confirm the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34195 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-34195 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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