TLS service impersonation via shared hard-coded key
Published Sep 29, 2025 · Updated Sep 29, 2025
Hard-coded TLS keys in Vasion Print Application before 20.0.2786 and Virtual Appliance Host before 22.0.1049 allow attackers to impersonate services. Multiple Docker images store the same readable pl-local.com private key and matching certificate at fixed /etc/ssl paths for TLS on ports 80 and 443. Container-level access is required to copy the key, after which attackers can decrypt captured traffic, forge certificates, or impersonate trusted appliance services.
Summary
What happened
Hard-coded TLS keys in Vasion Print Application before 20.0.2786 and Virtual Appliance Host before 22.0.1049 allow attackers to impersonate services. Multiple Docker images store the same readable pl-local.com private key and matching certificate at fixed /etc/ssl paths for TLS on ports 80 and 443. Container-level access is required to copy the key, after which attackers can decrypt captured traffic, forge certificates, or impersonate trusted appliance services.
The record
- CVE
- CVE-2025-34211
- Published
- Sep 29, 2025
- Updated
- Sep 29, 2025
- Vendor
- Vasion
- Product
- Vasion Print Application
- Classifications
- CWE-798, CWE-321, CAPEC-474, T1552.004
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Sep 29, 2025CVE publishedPublication date reported by the CVE source.
- Sep 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <20.0.2786
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Published Docker-container key extraction procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo