Horizon Alert
Summary of the vulnerability and why it matters
This vulnerability in Vasion Print's virtual appliance and application allows unauthenticated access to internal services, potentially leading to information disclosure, privilege escalation, or denial-of-service. The issue stems from a lack of authentication and network restrictions on the API gateway's proxy to internal Docker containers, exposing the internal service mesh as an attack surface.
- Internal services are exposed without controls.
- Leadership should remember its potential broad impact.
- Confirm relevance and exposure for your environment.
Attack Path
How an attacker could exploit the issue
An attacker can reach internal Vasion Print services by targeting the exposed Docker gateway, which lists and provides direct access to microservices without any authentication or rate limiting. This lack of security controls on the API gateway's proxy to internal Docker containers creates a wide attack surface. An attacker can then interact with these services, potentially leading to unauthorized access, privilege escalation within containers, or denial-of-service conditions on the appliance.
- Unauthenticated network access required.
- Exposed gateway API triggers vulnerability.
- Risk of information disclosure and escalation.
Live Threat
Current exploitation, exposure, and threat context
The Vasion Print Virtual Appliance and Application expose internal Docker containers and their services without authentication or network restrictions. This allows any attacker on the network or internet to enumerate all internal services and their versions, interact with their APIs as an unauthenticated user, and potentially cause information disclosure, privilege escalation within containers, or denial-of-service for the entire appliance.
- Internal services and their versions.
- Unauthenticated network access to APIs.
- Service disruption or information leakage.
Operational Fix
Recommended remediation, mitigation, and detection steps
The Vasion Print Virtual Appliance Host and Application are susceptible to an exposure of internal Docker containers. This vulnerability allows unauthenticated access to micro-services, potentially leading to information disclosure, privilege escalation, or denial-of-service. Action is required by teams managing the Vasion Print deployment. The first practical step is to identify all Vasion Print instances, confirm their network reachability and business criticality, and identify the accountable owner to plan remediation.
- Ownership: Vasion Print deployment owners.
- Verify: Network reachability and criticality.
- Action: Plan remediation based on risk.
