CVE-2025-34201
Published: 19 September 2025
Summary
CVE-2025-34201 is a high-severity Improper Isolation or Compartmentalization (CWE-653) vulnerability in Vasion Virtual Appliance Application. Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Remote System Discovery (T1018); ranked at the 22.0th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-30259
Vulnerability details
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,…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Lack of firewalling/segmentation between Docker containers enables remote system/service discovery (T1018, T1046, T1613), exploitation of internal services (HTTP, Redis, MySQL) for lateral movement (T1210) and privilege escalation (T1068) leading to system-wide compromise and data theft.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Defines isolation boundaries by specifying which external systems may access or process organization data.
Maintains isolation and compartmentalization by restricting flows between security domains or levels.
Reviewing the continued need for connections supports isolation and compartmentalization.
Locating systems away from hazards improves isolation and compartmentalization from external physical or environmental threats.
The CONOPS must articulate isolation and compartmentalization expectations for security and privacy, making architectural failures in separation of duties or domains harder to overlook.
Security architectures commonly incorporate isolation and compartmentalization strategies to limit the impact of compromises.
Organization-wide privacy program leadership ensures proper isolation and compartmentalization of personal data.
Oversight ensures data-matching activities maintain required isolation between distinct data sets and authorized user communities.