CVE-2025-34215
BaseFortify
Publication date: 2025-09-29
Last updated on: 2025-10-18
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| vasion | virtual_appliance_application | to 20.0.2702 (exc) |
| vasion | virtual_appliance_host | to 22.0.1026 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-306 | The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. |
| CWE-321 | The product uses a hard-coded, unchangeable cryptographic key. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-34215 is a critical remote code execution vulnerability in Vasion Print (formerly PrinterLogic) Virtual Appliance Host and Application for VA deployments. It occurs because the firmware update process is unauthenticated and exposes a public endpoint that returns a signed token. Additionally, every Docker image contains the appliance's private GPG key and a hard-coded passphrase. An attacker who extracts this key and obtains a token can decrypt, modify, re-sign, and upload malicious firmware, leading to remote code execution on the appliance. [1]
How can this vulnerability impact me? :
This vulnerability allows an attacker to remotely execute arbitrary code on the affected Vasion Print appliance without authentication. This can lead to full compromise of the appliance, including unauthorized access, data manipulation, disruption of printing services, and potential lateral movement within the network. The high severity and ease of exploitation make it a significant security risk. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately update Vasion Print Virtual Appliance Host to version 22.0.1026 or later, and the Print Application to version 20.0.2702 or later for VA deployments. Additionally, restrict access to the firmware update endpoint to prevent unauthenticated access and monitor for any unauthorized firmware update attempts. [1]