dbcve.org
Virtual Appliance ApplicationApplication · Vasion

CVE-2025-34207

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
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 22.0.1049 and Application prior to 20.0.2786 (VA and SaaS deployments) configure the SSH client within Docker instances with the following options: `UserKnownHostsFile=/dev/null`, `StrictHostKeyChecking=no`, and `ForwardAgent yes`. These settings disable verification of the remote host’s SSH key and automatically forward the developer’s SSH‑agent to any host that matches the configured wildcard patterns. As a result, an attacker who can reach a single compromised container can cause the container to connect to a malicious SSH server, capture the forwarded private keys, and use those keys for unrestricted lateral movement across the environment. This vulnerability has been identified by the vendor as: V-2024-027 — Insecure Secure Shell (SSH) Configuration.

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 and Application configure SSH clients within Docker containers with insecure settings: UserKnownHostsFile=/dev/null disables host key verification, StrictHostKeyChecking=no accepts any host, and ForwardAgent yes forwards SSH keys to any matching host. An attacker who compromises a single container can redirect SSH connections to a malicious server to capture forwarded private keys and move laterally.

MitigationDisable SSH agent forwarding by default and remove wildcard patterns; configure strict host key checking using a known_hosts file; restrict ForwardAgent to specific, verified hosts only.

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 read the version file or use the product's built-in version check command. Typical paths include /opt/vasion/version or check via the web UI under System > About.
    Affected if version is lower than 20.0.2786
  2. Check Vasion Virtual Appliance Host version
    Locate the host system version via command line (cat /etc/version) or through the virtualization platform's guest info.
    Affected if version is lower than 22.0.1049
  3. Inspect SSH client config for disabled host key verification
    Examine SSH client configuration files inside Docker containers: grep -r 'UserKnownHostsFile.*=/dev/null' /etc/ssh/ssh_config ~/.ssh/config or similar paths within the container filesystem.
    Affected if UserKnownHostsFile is set to /dev/null in any SSH client config
  4. Inspect SSH client config for StrictHostKeyChecking=no
    Search SSH configuration for the StrictHostKeyChecking directive: grep -r 'StrictHostKeyChecking.*no' /etc/ssh/ssh_config ~/.ssh/config or within Docker container configs.
    Affected if StrictHostKeyChecking is set to 'no' in any SSH client config
  5. Inspect SSH client config for ForwardAgent setting
    Search SSH configuration for agent forwarding: grep -r 'ForwardAgent.*yes' /etc/ssh/ssh_config ~/.ssh/config or within Docker container configs.
    Affected if ForwardAgent is set to 'yes' in any SSH client config

User is affected if running a version below 20.0.2786 (Application) or below 22.0.1049 (Host) AND any of the insecure SSH settings (UserKnownHostsFile=/dev/null, StrictHostKeyChecking=no, or ForwardAgent yes) are present in Docker container SSH configurations.

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

Disable SSH agent forwarding by default and remove wildcard patterns; configure strict host key checking using a known_hosts file; restrict ForwardAgent to specific, verified hosts only.

Recommended fix High confidence

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

  1. Identify whether you need to update Virtual Appliance Application, Virtual Appliance Host, or both components
  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 SSH configuration in Docker instances no longer contains UserKnownHostsFile=/dev/null, StrictHostKeyChecking=no, or ForwardAgent yes
  5. Test SSH functionality to ensure legitimate operations continue to work correctly after the upgrade

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

Fix this in Virtual Appliance Application Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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