# CVE-2025-34207: Vasion Print (formerly PrinterLogic) Insecure SSH Client Configuration

> Insecure SSH client settings in Vasion Print allow attackers to capture forwarded keys and move laterally across the environment.

- **Severity:** High 7.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-8v7v-hv29-cp2f

## What is CVE-2025-34207?

CVE-2025-34207 is a high-severity vulnerability in Vasion Print Application, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-34207?

It affects 2 products.


Products: Vasion Virtual Appliance Application, Vasion Virtual Appliance Host.

## How do I fix CVE-2025-34207?

No fix has been published for CVE-2025-34207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-34207 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34207 exists.

## Other vulnerabilities in Vasion Print Application

- [CVE-2025-34217](https://insights.sbomify.com/CVE-2025-34217/): Vasion Print (formerly PrinterLogic) Undocumented Hardcoded SSH Key (critical 10.0)
- [CVE-2025-34216](https://insights.sbomify.com/CVE-2025-34216/): Vasion Print (formerly PrinterLogic) RCE and Password Leaks via API (critical 10.0)
- [CVE-2025-34218](https://insights.sbomify.com/CVE-2025-34218/): Vasion Print (formerly PrinterLogic) Exposed Internal Docker Instance (critical 10.0)
- [CVE-2025-34221](https://insights.sbomify.com/CVE-2025-34221/): Vasion Print (formerly PrinterLogic) (critical 10.0)
- [CVE-2025-34222](https://insights.sbomify.com/CVE-2025-34222/): Vasion Print (formerly PrinterLogic) Unauthenticated Admin APIs Used to Modify SSL Certificates (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34207 and fix it if it is affected.

What it is: CVE-2025-34207 is a high-severity vulnerability in Vasion Print Application, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34207 exists.

Affected product: Vasion Print Application. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-34207/ (Markdown: https://insights.sbomify.com/CVE-2025-34207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34207
- OSV: https://osv.dev/vulnerability/CVE-2025-34207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-34207/
Summaries are generated and may contain mistakes; the official description above is the record.