CVE-2025-34218
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-29

Last updated on: 2025-10-09

Assigner: VulnCheck

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).
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-29
Last Modified
2025-10-09
Generated
2026-05-07
AI Q&A
2025-09-29
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
vasion virtual_appliance_application to 20.0.2786 (exc)
vasion virtual_appliance_host to 22.0.1049 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-34218 is a critical vulnerability in Vasion Print (formerly PrinterLogic) products where internal Docker containers are exposed through the gateway Docker instance without any authentication, access control, or rate limiting. This exposure allows attackers on the LAN or Internet to enumerate all internal microservice containers and their versions, interact with their APIs as unauthenticated users, and potentially perform malicious actions such as information disclosure, privilege escalation within containers, or denial-of-service attacks. The root cause is the lack of authentication and network restrictions on the API gateway proxy to internal Docker containers, effectively making the internal service mesh publicly accessible. [1]


How can this vulnerability impact me? :

This vulnerability can have severe impacts including unauthorized disclosure of sensitive information, attackers gaining elevated privileges within containers, and denial-of-service conditions affecting the entire appliance. Because the internal Docker containers are exposed without authentication or access controls, attackers can exploit these weaknesses remotely or locally, potentially compromising the confidentiality, integrity, and availability of the affected systems. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by checking if the /meta endpoint of the gw Docker instance is accessible without authentication on your network or system. You can use commands like curl or wget to query the endpoint and see if it returns a list of internal micro-service containers and their version information. For example: curl http://<device-ip-or-hostname>/meta or wget -qO- http://<device-ip-or-hostname>/meta. If the endpoint is reachable and returns container information without requiring authentication, the system is vulnerable. [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include upgrading the Vasion Print Virtual Appliance Host to version 22.0.1049 or later and the Print Application to version 20.0.2786 or later, as these versions address the vulnerability. Additionally, restrict network access to the gw Docker instance by implementing access control lists (ACLs), authentication mechanisms, and rate limiting to prevent unauthenticated access to the /meta endpoint and internal Docker containers. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart