dbcve.org
Virtual Appliance ApplicationApplication · Vasion

CVE-2025-34221

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 25.2.169 / 25.2.1518 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 25.2.169 and Application prior to version 25.2.1518 (VA/SaaS deployments) expose every internal Docker container to the network because firewall rules allow unrestricted traffic to the Docker bridge network. Because no authentication, ACL or client‑side identifier is required, the attacker can interact with any internal API, bypassing the product’s authentication mechanisms entirely. The result is unauthenticated remote access to internal services, allowing credential theft, configuration manipulation and potential remote code execution. This vulnerability has been identified by the vendor as: V-2025-002 — Authentication Bypass - Docker Instances.

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 to the network due to firewall rules allowing unrestricted traffic to the Docker bridge network. This allows unauthenticated attackers to bypass all authentication mechanisms and directly interact with internal APIs, enabling credential theft, configuration changes, and potential remote code execution.

MitigationUpgrade to Vasion Print Virtual Appliance Host version 25.2.169 or Application version 25.2.1518 (VA/SaaS). Alternatively, implement strict firewall rules to restrict access to the Docker bridge network and internal container APIs.

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:< 25.2.1518
Virtual Appliance HostApplication
Affected:< 25.2.169

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
    Access the Vasion admin interface or check system information to determine the installed Application version number
    Affected if Version is lower than 25.2.1518
  2. Check Vasion Virtual Appliance Host version
    Access the Vasion host system or check virtualization platform for the host version
    Affected if Version is lower than 25.2.169
  3. Verify firewall rules for Docker bridge network
    Inspect firewall configuration to determine if unrestricted inbound traffic is permitted to the Docker network range (typically 172.17.0.0/16)
    Affected if Firewall allows unrestricted traffic to Docker bridge network
  4. Confirm Docker API exposure
    Check if the Docker API port (commonly 2375 or 2376) is accessible from untrusted network interfaces
    Affected if Docker API is exposed to external or untrusted networks

Environment is affected if either the Application version is below 25.2.1518 or the Host version is below 25.2.169, AND firewall rules permit unrestricted access to the Docker bridge network or internal container APIs.

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 25.2.169 / 25.2.1518 or later
Fixed in 25.2.16925.2.1518
Interim mitigation

Upgrade to Vasion Print Virtual Appliance Host version 25.2.169 or Application version 25.2.1518 (VA/SaaS). Alternatively, implement strict firewall rules to restrict access to the Docker bridge network and internal container APIs.

Recommended fix High confidence

Virtual Appliance Host 25.2.169 and Virtual Appliance Application 25.2.1518 (or later)

  1. Upgrade Virtual Appliance Host to version 25.2.169 or later
  2. Upgrade Virtual Appliance Application to version 25.2.1518 or later
  3. After upgrading, verify that firewall rules no longer allow unrestricted access to the Docker bridge network
  4. Confirm that internal Docker container APIs now require proper authentication

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34221 — 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-34221 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