CVE-2025-34222: Vasion Print (formerly PrinterLogic) Unauthenticated Admin APIs Used to Modify SSL Certificates
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.
Security readout for executives and security teams
Plain-English summary
This flaw lets an unauthenticated network attacker use Vasion Print admin certificate functions. They could replace trusted certificates, delete certificates that services depend on, or retrieve stored CA and client certificates. That can break trust relationships or enable serious compromise of printing infrastructure.
Executive priority
Treat as urgent for any affected deployment. The issue combines no authentication, certificate trust impact, and CVSS 10 severity, so remediation should be prioritized ahead of routine patching.
Technical view
Vasion Print VA Host before 22.0.1049 and Application before 20.0.2786 expose certificate admin routes without authentication. The reported routes map to HPCertificateController, which lacks user validation. The service-client certificate endpoint also has IDOR-style enumeration risk.
Likely exposure
Exposure is likely limited to organizations running affected Vasion Print VA or SaaS deployments where the named admin routes are reachable over the network. The bundle does not prove internet-wide exposure for any specific customer environment.
Exploitation context
The source bundle reports unauthenticated access to certificate upload, delete, CA download, and service-client certificate endpoints. CISA KEV status is false, and the provided sources do not state confirmed active exploitation.
Researcher notes
Evidence comes from the CVE record, vendor bulletins, Pierre Kim’s technical write-up, and VulnCheck. The bundle identifies vendor issue V-2024-028. Do not assume exploitation unless new KEV or vendor intelligence confirms it.
Mitigation direction
Upgrade affected deployments to vendor-fixed versions or later: VA Host 22.0.1049 and Application 20.0.2786.
Review Vasion security bulletins for deployment-specific remediation instructions.
Restrict network access to Vasion Print administrative surfaces until remediation is verified.
Rotate exposed or untrusted certificates if suspicious access or certificate retrieval is found.
Preserve logs before remediation for incident review.
Validation and detection
Confirm whether any Vasion Print VA/SaaS deployment is below host 22.0.1049 or application 20.0.2786.
Review HTTP logs for access to the four named certificate admin paths.
Check certificate stores for unexpected CA, service-client, or recently deleted certificates.
Validate authentication controls on those routes in a staging or approved test window.
Correlate suspicious certificate changes with administrative change records.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.