Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 25.1.102 and Application prior to version 25.1.1413 (Windows client deployments) contain a registry key that can be enabled by administrators, causing the client to skip SSL/TLS certificate validation. An attacker who can intercept HTTPS traffic can then inject malicious driver DLLs, resulting in remote code execution with SYSTEM privileges; a local attacker can achieve local privilege escalation via a junction‑point DLL injection. This vulnerability has been confirmed to be remediated, but it is unclear as to when the patch was introduced.
Security readout for executives and security teams
Plain-English summary
This flaw can turn a printer-management client into a full system compromise path. If the certificate-validation bypass is enabled, an attacker able to intercept HTTPS traffic may cause malicious driver DLLs to run as SYSTEM. The issue is reported as remediated, but patch-introduction timing is unclear.
Executive priority
Treat this as urgent for organizations running affected Vasion Print Windows client deployments. The impact is full endpoint control, but real-world urgency depends on version, registry configuration, and network interception exposure.
Technical view
Vasion Print, formerly PrinterLogic, VA Host before 25.1.102 and Windows client Application before 25.1.1413 can skip SSL/TLS certificate validation via an administrator-enabled registry key. That can permit malicious driver DLL injection over intercepted HTTPS, causing RCE as SYSTEM. A local privilege-escalation path via junction-point DLL injection is also described.
Likely exposure
Most relevant exposure is Windows client deployments using Vasion Print/PrinterLogic with older VA Host or Application versions, especially where the certificate-validation bypass registry key was enabled for operations or troubleshooting.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked KEV. Exploitation requires specific conditions: certificate validation must be bypassed and the attacker must intercept HTTPS traffic, or have local access for the LPE path.
Researcher notes
The strongest evidence is the CVE description, vendor bulletin references, and VulnCheck advisory. Evidence is incomplete on the exact patch-introduction date. Do not assume exploitation in the wild from the provided bundle.
Mitigation direction
Upgrade VA Host to 25.1.102 or later where applicable.
Upgrade Windows client Application to 25.1.1413 or later where applicable.
Ensure the certificate-validation bypass registry key is not enabled.
Review Vasion security bulletins for exact fixed-release guidance.
Limit opportunities to intercept client-to-appliance HTTPS traffic.
Investigate suspicious printer driver DLL changes on Windows clients.
Validation and detection
Inventory Vasion Print VA Host and Windows client Application versions.
Check whether any certificate-validation bypass registry key is enabled.
Confirm vendor advisory status for your deployed release line.
Review endpoint logs for unexpected driver DLL installation activity.
Verify clients reject invalid or untrusted TLS certificates.
Prioritize systems where print clients run with SYSTEM privileges.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-295 · source CWE mapping
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.