CVE-2025-34229: Vasion Print (formerly PrinterLogic) Blind SSRF via HP installApp.php
Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 25.1.102 and Application prior to version 25.1.1413 (VA/SaaS deployments) contain a blind server-side request forgery (SSRF) vulnerability reachable via the /var/www/app/console_release/hp/installApp.php script that can be exploited by an unauthenticated user. When a printer is registered, the software stores the printer’s host name in the variable $printer_vo->str_host_address. The code later builds a URL like 'http://<host‑address>:80/DevMgmt/DiscoveryTree.xml' and sends the request with curl. No validation, whitelist, or private‑network filtering is performed before the request is made. Because the request is blind, an attacker cannot see the data directly, but can still: probe internal services, trigger internal actions, or gather other intelligence. This vulnerability has been confirmed to be remediated, but it is unclear as to when the patch was introduced.
Security readout for executives and security teams
Plain-English summary
CVE-2025-34229 lets an unauthenticated attacker make affected Vasion Print systems send hidden web requests to chosen hosts. The attacker does not directly see responses, but the flaw can still expose internal service presence or trigger reachable internal endpoints. Treat it as a network-mapping and internal-access risk for print infrastructure.
Executive priority
Prioritize remediation in environments where Vasion Print can reach sensitive internal systems. The flaw is medium severity, unauthenticated, and publicly documented, but evidence of active exploitation is not provided.
Technical view
Affected Vasion Print VA/SaaS versions build a curl request to a printer host for HP discovery without validating the hostname, allowlist, or private-network targets. The issue is blind SSRF in /var/www/app/console_release/hp/installApp.php. Sources list remediation before VA Host 25.1.102 and Application 25.1.1413, though patch timing is unclear.
Likely exposure
Exposure is most likely where Vasion Print Virtual Appliance Host or SaaS Application versions predate 25.1.102 or 25.1.1413. Risk rises if unauthenticated users can reach affected printer registration or management workflows and the server can reach sensitive internal networks.
Exploitation context
The bundle reports unauthenticated exploitability and blind SSRF behavior, but does not cite active exploitation. The CVE is not marked KEV. Public technical details exist, so defenders should assume motivated researchers can understand the bug without needing response visibility.
Researcher notes
Key evidence supports blind SSRF through unsanitized printer host handling and curl-based HP discovery. Affected version metadata in the bundle is inconsistent, so rely on the narrative version thresholds and vendor bulletins when validating exposure.
Mitigation direction
Upgrade VA Host to 25.1.102 or later where applicable.
Upgrade Vasion Print Application to 25.1.1413 or later where applicable.
Review Vasion VA and SaaS security bulletins for current vendor guidance.
Restrict external access to Vasion Print administrative and registration surfaces.
Limit Vasion server outbound access to required internal destinations.
Validation and detection
Inventory Vasion Print VA and SaaS deployments and record exact versions.
Confirm VA Host version is 25.1.102 or later where applicable.
Confirm Application version is 25.1.1413 or later where applicable.
Review access logs for unusual printer registration or HP discovery activity.
Check outbound network logs from Vasion servers to unexpected internal hosts.
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-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 CVE wording references SSRF or metadata access, so cloud discovery and credential material 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.
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.
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.