CVE-2025-34201
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-19

Last updated on: 2025-09-24

Assigner: VulnCheck

Description
Vasion Print (formerly PrinterLogic) Virtual Appliance Host and Application (VA and SaaS deployments) run many Docker containers on shared internal networks without firewalling or segmentation between instances. A compromise of any single container allows direct access to internal services (HTTP, Redis, MySQL, etc.) on the overlay network. From a compromised container, an attacker can reach and exploit other services, enabling lateral movement, data theft, and system-wide compromise.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-19
Last Modified
2025-09-24
Generated
2026-06-16
AI Q&A
2025-09-19
EPSS Evaluated
2026-06-14
NVD
CVE-2025-34201
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
vasion virtual_appliance_application *
vasion virtual_appliance_host *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-653 The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability affects Vasion Print (formerly PrinterLogic) Virtual Appliance Host and Application deployments that run many Docker containers on shared internal networks without proper firewalling or segmentation between instances. Because of this lack of network isolation, if an attacker compromises any single container, they can directly access internal services such as HTTP, Redis, and MySQL on the overlay network. This allows the attacker to move laterally between containers, potentially exploiting other services and leading to data theft or a system-wide compromise. [1]

Impact Analysis

The vulnerability can lead to unauthorized lateral movement within the containerized environment, allowing an attacker who compromises one container to access and exploit other internal services. This can result in data theft, unauthorized access to sensitive information, and potentially a full system compromise, affecting the confidentiality, integrity, and availability of the affected systems. [1]

Detection Guidance

Detection involves identifying Docker containers running on shared internal networks without proper firewalling or segmentation. You can inspect Docker networks and container connections to check for lack of isolation. Commands such as 'docker network ls' to list networks, 'docker network inspect <network_name>' to view connected containers, and 'docker ps' to list running containers can help. Additionally, monitoring network traffic between containers for unauthorized access attempts may indicate exploitation. [1]

Mitigation Strategies

Immediate mitigation steps include implementing network segmentation and firewall rules between Docker containers to prevent lateral movement. Restrict container communication to only necessary services and isolate containers on separate networks where possible. Review and apply any vendor security bulletins or patches if available. Limiting privileges of containers and monitoring for suspicious activity are also recommended. [1]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-34201. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart