CVE-2025-34191
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-19

Last updated on: 2025-10-02

Assigner: VulnCheck

Description
Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 22.0.843 and Application prior to 20.0.1923 (macOS/Linux client deployments) contain an arbitrary file write vulnerability via the response file handling. When tasks produce output the service writes response data into files under /opt/PrinterInstallerClient/tmp/responses/ reusing the requested filename. The service follows symbolic links in the responses directory and writes as the service user (typically root), allowing a local, unprivileged user to cause the service to overwrite or create arbitrary files on the filesystem as root. This can be used to modify configuration files, replace or inject binaries or drivers, and otherwise achieve local privilege escalation and full system compromise. This vulnerability has been identified by the vendor as: V-2023-019 — Arbitrary File Write as Root.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-19
Last Modified
2025-10-02
Generated
2026-05-07
AI Q&A
2025-09-19
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
vasion virtual_appliance_application to 20.0.1923 (exc)
vasion virtual_appliance_host to 22.0.843 (exc)
apple macos *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-276 During installation, installed file permissions are set to allow anyone to modify those files.
CWE-59 The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-34191 is an arbitrary file write vulnerability in Vasion Print (formerly PrinterLogic) Virtual Appliance Host and Application versions prior to specified versions. It occurs because the service writes response data into files under a directory that follows symbolic links, allowing a local, unprivileged user to overwrite or create arbitrary files on the filesystem with root privileges. This can lead to modification of configuration files, replacement or injection of binaries or drivers, resulting in local privilege escalation and full system compromise. [1]


How can this vulnerability impact me? :

This vulnerability can allow a local attacker with limited privileges to escalate their privileges to root by exploiting the arbitrary file write flaw. The attacker can overwrite or create critical system files, modify configurations, or inject malicious binaries or drivers, potentially leading to full system compromise, loss of confidentiality, integrity, and availability of the affected system. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

Detection involves checking for the presence of vulnerable versions of Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to 22.0.843 and Application prior to 20.0.1923 on macOS/Linux clients. Additionally, inspecting the /opt/PrinterInstallerClient/tmp/responses/ directory for symbolic links that could be exploited is recommended. Commands to help detect this include: 1) Checking installed versions: `rpm -qa | grep PrinterLogic` or `dpkg -l | grep PrinterLogic` on Linux, or checking application version on macOS. 2) Listing symbolic links in the responses directory: `find /opt/PrinterInstallerClient/tmp/responses/ -type l -ls` to identify suspicious symlinks that could be exploited for arbitrary file writes. [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include upgrading the Vasion Print Virtual Appliance Host to version 22.0.843 or later and the Print Application to version 20.0.1923 or later. Additionally, restrict local user access to the /opt/PrinterInstallerClient/tmp/responses/ directory to prevent creation or manipulation of symbolic links. Applying vendor security patches as soon as they are available is critical to prevent exploitation of this arbitrary file write vulnerability. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart