dbcve.org
Virtual Appliance ApplicationApplication · Vasion

CVE-2025-34218

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 20.0.2786 / 22.0.1049 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Vasion Print Virtual Appliance exposes internal Docker containers through the gw Docker instance's /meta endpoint without authentication, ACLs, or rate-limiting. Attackers can enumerate all microservices and versions, interact with unauthenticated APIs, and potentially achieve information disclosure, privilege escalation, or denial of service.

MitigationUpgrade to version 22.0.1049 (Virtual Appliance) or 20.0.2786 (Application), and implement network-level access controls and authentication on the API gateway proxy to internal containers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Virtual Appliance ApplicationApplication
Affected:< 20.0.2786
Virtual Appliance HostApplication
Affected:< 22.0.1049

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Vasion Virtual Appliance Application version
    Locate and inspect the installed Vasion Virtual Appliance Application version using the product's admin interface, system information page, or version lookup command provided by the appliance
    Affected if The installed Application version is below 20.0.2786
  2. Check Vasion Virtual Appliance Host version
    Locate and inspect the Vasion Virtual Appliance Host version through the hypervisor, system utilities, or appliance management console
    Affected if The installed Host version is below 22.0.1049
  3. Test accessibility of the /meta endpoint
    Attempt to access the /meta endpoint on the gw Docker instance gateway using HTTP or HTTPS (e.g., http://<appliance-ip>/meta or the Docker gateway IP on port 80/443)
    Affected if The /meta endpoint returns a listing of microservices with version information without requiring authentication
  4. Verify direct access to internal Docker containers
    Attempt to access internal microservice containers directly over HTTP/HTTPS using their Docker network IPs or host ports without any authentication, ACL, or rate-limiting
    Affected if Internal Docker containers are reachable directly without any authentication or access controls

The environment is affected if either the Application version is below 20.0.2786 or the Host version is below 22.0.1049, and the /meta endpoint or internal Docker containers are accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 20.0.2786 / 22.0.1049 or later
Fixed in 20.0.278622.0.1049
Interim mitigation

Upgrade to version 22.0.1049 (Virtual Appliance) or 20.0.2786 (Application), and implement network-level access controls and authentication on the API gateway proxy to internal containers.

Recommended fix High confidence

Virtual Appliance Application: 20.0.2786 or later; Virtual Appliance Host: 22.0.1049 or later

  1. Identify which Virtual Appliance components are deployed: Application, Host, or both
  2. For Virtual Appliance Application: upgrade to version 20.0.2786 or later
  3. For Virtual Appliance Host: upgrade to version 22.0.1049 or later
  4. After upgrading, verify the /meta endpoint is no longer publicly accessible
  5. Verify internal Docker containers are no longer reachable directly without authentication
  6. Confirm that API gateway now properly enforces access controls on proxied internal services

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Virtual Appliance Application Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34218 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34218 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data