CVE-2025-34207: Vasion Print (formerly PrinterLogic) Insecure SSH Client Configuration

Published Sep 29, 2025
·
Updated

Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to 22.0.1049 and Application prior to 20.0.2786 (VA and SaaS deployments) configure the SSH client within Docker instances with the following options: UserKnownHostsFile=/dev/null, StrictHostKeyChecking=no, and ForwardAgent yes. These settings disable verification of the remote host’s SSH key and automatically forward the developer’s SSH‑agent to any host that matches the configured wildcard patterns. As a result, an attacker who can reach a single compromised container can cause the container to connect to a malicious SSH server, capture the forwarded private keys, and use those keys for unrestricted lateral movement across the environment. This vulnerability has been identified by the vendor as: V-2024-027 — Insecure Secure Shell (SSH) Configuration.

Affected Software

4 affected components
Vasion Print<22.0.1049
Vasion Print<20.0.2786
Vasion Virtual Appliance Application<20.0.2786
Vasion Virtual Appliance Host<22.0.1049

Event History

Sep 29, 2025
CVE Published
via MITRE·08:38 PM
Data Sourced
via MITRE·08:38 PM
DescriptionWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeaknessAffected Software
May 9, 58339
Event
via NVD·11:36 PM

Frequently Asked Questions

1

What is the severity of CVE-2025-34207?

CVE-2025-34207 is rated as a serious vulnerability due to its misconfiguration of SSH settings in Vasion Print software.

2

How can I mitigate the effects of CVE-2025-34207?

To mitigate CVE-2025-34207, users should update Vasion Print to version 22.0.1049 or later, and 20.0.2786 or later for the application.

3

What systems are affected by CVE-2025-34207?

CVE-2025-34207 affects Vasion Print Virtual Appliance Host prior to version 22.0.1049 and the Application prior to version 20.0.2786.

4

Is there a known exploit for CVE-2025-34207?

As of now, there are no publicly known exploits specifically targeting CVE-2025-34207.

5

What should I do if I can't update to the latest version to resolve CVE-2025-34207?

If updating is not possible, consider disabling SSH access to Docker instances as a temporary workaround for CVE-2025-34207.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203