CVE-2025-34217
BaseFortify
Publication date: 2025-09-30
Last updated on: 2025-10-07
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| vasion | virtual_appliance_application | * |
| vasion | virtual_appliance_host | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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?
This vulnerability involves Vasion Print (formerly PrinterLogic) Virtual Appliance Host and Application deployments containing an undocumented 'printerlogic' user with a hardcoded SSH public key in the authorized_keys file. Because of a sudoers rule granting the printerlogic_ssh group passwordless root privileges, anyone possessing the matching private SSH key can gain root access to the appliance. This is classified as a use of a hard-coded cryptographic key vulnerability (CWE-321). [1]
How can this vulnerability impact me? :
An attacker who obtains the private SSH key corresponding to the hardcoded public key can gain root access to the Vasion Print appliance without authentication. This allows full control over the system, potentially leading to data breaches, system compromise, and disruption of services. The vulnerability has a maximum CVSS v4 base score of 10.0, indicating critical impact on confidentiality, integrity, and availability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection involves checking the presence of the undocumented 'printerlogic' user and its hardcoded SSH public key in the '~/.ssh/authorized_keys' file on the Vasion Print appliance. You can run commands to list users and inspect SSH authorized keys, for example: 1) Check for the 'printerlogic' user: `getent passwd | grep printerlogic` 2) Inspect the authorized_keys file for the printerlogic user: `cat /home/printerlogic/.ssh/authorized_keys` or `cat /root/.ssh/authorized_keys` if applicable. Additionally, check sudoers rules for the 'printerlogic_ssh' group with: `sudo cat /etc/sudoers` or `sudo cat /etc/sudoers.d/*` to find any 'NOPASSWD: ALL' entries related to this group. These steps help identify if the vulnerable configuration exists on your system. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include removing or disabling the undocumented 'printerlogic' user and its hardcoded SSH public key from the appliance. Specifically, remove the hardcoded public key from the '~/.ssh/authorized_keys' file and revoke any sudoers rules granting passwordless root access to the 'printerlogic_ssh' group. If possible, rotate SSH keys and enforce strict access controls. Monitor vendor security bulletins for patches or updates addressing this vulnerability and apply them as soon as they become available. [1]