Horizon Alert
Summary of the vulnerability and why it matters
This advisory concerns a critical vulnerability in Vasion Print's virtual appliance and application that allows for man-in-the-middle attacks, potentially exposing sensitive data and enabling malicious activity. The issue stems from the product's default configuration and code patterns that disable secure communication verification.
- Insecure defaults allow data interception and modification.
- Leadership should remember the risk to sensitive print data.
- Confirm if this print management tool is in use.
Attack Path
How an attacker could exploit the issue
An attacker can intercept network traffic between the Vasion Print virtual appliance and its printers or internal services. This allows them to view or alter sensitive data, insert malicious code, or disrupt services by exploiting the product's failure to verify TLS/SSL certificates.
- Intercept network traffic.
- Disable TLS/SSL certificate verification.
- Eavesdrop, modify data, inject payloads.
Live Threat
Current exploitation, exposure, and threat context
This vulnerability could allow an attacker to intercept and modify sensitive data exchanged between the Vasion Print application and printers or internal services when network traffic is not properly secured. This occurs because the application may disable TLS/SSL certificate verification, enabling man-in-the-middle attacks.
- Print jobs and authentication tokens at risk.
- On-path network interception.
- Data eavesdropping and modification.
Operational Fix
Recommended remediation, mitigation, and detection steps
The Vasion Print (formerly PrinterLogic) Virtual Appliance Host and Application are susceptible to Man-in-the-Middle attacks due to disabled TLS/SSL certificate verification. This allows attackers to intercept and modify sensitive data, including print jobs and authentication tokens, or disrupt services. Responsibility likely falls to application owners, infrastructure teams, and potentially network/security teams to identify affected deployments, confirm business criticality and reachability, and then coordinate remediation.
- Application and Infrastructure teams own remediation.
- Verify affected deployments and business criticality.
- Plan vendor coordination and maintenance windows.