CVE-2025-34222·Docker vulnerability
Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 22.0.1049 and Application prior to version 20.0.2786 (VA/SaaS deployments) expose four admin routes – /admin/hp/cert_upload, /admin/hp/cert_delete, /admin/certs/ca, and /admin/certs/serviceclients/{scid} – without any authentication check. The routes are defined in the /var/www/app/routes/web.php file inside the printercloud/pi Docker container and are handled by the HPCertificateController class, which performs no user validation. An unauthenticated attacker can therefore upload a new TLS/SSL certificate replacing the trusted root used by the appliance, delete an existing certificate causing immediate loss of trust for services that rely on it, or download any stored CA or client certificate via the service‑clients endpoint which also suffers an IDOR that allows enumeration of all client IDs. This vulnerability has been identified by the vendor as: V-2024-028 — Unauthenticated Admin APIs Used to Modify SSL Certificates.
- Severity
- critical
- Software
- Docker
- Fixed in
- 22.0.1049
- Published
- 2025-09-29
Affected versions
Until: 22.0.1049
Fixed in: 22.0.1049
How to fix this CVE
Update Docker to version 22.0.1049 or later to patch the unauthenticated certificate management endpoints in Vasion Print Virtual Appliance. If you are running a containerized Vasion Print deployment using Docker, ensure your host system Docker installation is current, and verify that your Vasion Print container image version is 22.0.1049 or above. Additionally, review network access controls to restrict admin API endpoints to trusted sources only.
sudo dnf update docker-ceDefensia detects this vulnerability
What an exploitation attempt looks like
Sample log line indicative of exploitation attempts:
POST|DELETE|GET /admin/hp/cert_upload|/admin/hp/cert_delete|/admin/certs/ca|/admin/certs/serviceclients/\d+ HTTP/1\.1.*(?!Authorization|X-API-Key)WAF mitigation (if patching is not yet possible)
Add this rule to your WAF to block exploitation attempts while you schedule the patch.
Implement authentication middleware that requires valid API credentials (JWT, API key, or session token) for all requests matching patterns: ^/admin/hp/cert_(upload|delete)$, ^/admin/certs/ca$, and ^/admin/certs/serviceclients/. Return 401 Unauthorized for requests lacking valid credentials. Additionally, implement rate limiting on these endpoints and log all access attempts for audit trails.How to check if you are affected
- Check your Docker version: docker --version
- Verify Vasion Print container version: docker inspect <container-id> | grep -i version or docker ps --format 'table {{.Image}}'
- Search for suspicious certificate upload/delete requests in Docker daemon logs: sudo journalctl -u docker -g 'admin/hp/cert' or check /var/log/docker.log for POST/DELETE requests to /admin/hp/cert_upload, /admin/hp/cert_delete, /admin/certs/ca, or /admin/certs/serviceclients
- Verify the fix by confirming Vasion Print version is 22.0.1049 or later: docker exec <container-id> cat /opt/app/VERSION or equivalent version file location
Indicators of compromise
- /admin/hp/cert_upload
- /admin/hp/cert_delete
- /admin/certs/ca
- /admin/certs/serviceclients
FAQ
What is CVE-2025-34222?
CVE-2025-34222 is a critical authentication bypass vulnerability in Vasion Print (formerly PrinterLogic) Virtual Appliance that allows unauthenticated attackers to upload, delete, or download TLS/SSL certificates through exposed admin API endpoints. This permits attackers to compromise certificate trust, intercept encrypted traffic, or enumerate sensitive client information.
Is CVE-2025-34222 being actively exploited?
No, CVE-2025-34222 is not currently listed on CISA's Known Exploited Vulnerabilities (KEV) catalog and has no public exploit available. However, the attack surface is trivial and requires no authentication, making it high-risk if exposed to untrusted networks.
What versions of Docker are affected by CVE-2025-34222?
This CVE specifically affects Vasion Print Virtual Appliance versions prior to 22.0.1049 and Application versions prior to 20.0.2786 running inside Docker containers. Update your Vasion Print container image to version 22.0.1049 or later. The Docker engine itself is not directly vulnerable; the issue lies in the containerized application.
How do I check if my server is vulnerable to CVE-2025-34222?
Run `docker ps --format 'table {{.Image}}'` to list running containers and identify Vasion Print instances, then use `docker inspect <container-id> | grep -E 'Image|Version'` to confirm the version is below 22.0.1049. Additionally, test network accessibility to /admin/hp/cert_upload without authentication using `curl -X POST http://<host>/admin/hp/cert_upload` — if it responds without a 401/403 error, the endpoint is exposed.
Does Defensia detect CVE-2025-34222?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server and Vasion Print containers are running, CVE-2025-34222 will appear in your dashboard with remediation steps.
Related Docker CVEs
References
- https://help.printerlogic.com/saas/Print/Security/Security-Bulletins.htm
- https://help.printerlogic.com/va/Print/Security/Security-Bulletins.htm
- https://pierrekim.github.io/blog/2025-04-08-vasion-printerlogic-83-vulnerabilities.html#va-insecure-apis-02
- https://www.vulncheck.com/advisories/vasion-print-printerlogic-unauth-admin-apis-used-to-modify-ssl-certs
- https://pierrekim.github.io/blog/2025-04-08-vasion-printerlogic-83-vulnerabilities.html#va-insecure-apis-02
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-34222. Free for 1 server.
Get started free