Security readout for executives and security teams
Plain-English summary
Vasion Print could be tricked into making network requests from its own server to attacker-chosen hostnames stored as printer addresses. The attacker does not see the response, but could still map internal services or cause internal systems to receive requests.
Executive priority
Treat this as a timely upgrade and exposure review, not an emergency absent exploitation evidence. Prioritize internet-facing or broadly reachable Vasion Print deployments.
Technical view
An unauthenticated blind SSRF exists in /var/www/app/console_release/hp/log_off_single_sign_on.php. The application uses $printer_vo->str_host_address to build an HTTP request to /DevMgmt/DiscoveryTree.xml with curl, without validation, allowlisting, or private-network filtering.
Likely exposure
Organizations running Vasion Print Virtual Appliance Host before 25.1.102 or Print Application before 25.1.1413 in VA or SaaS deployments should assess exposure.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation is unauthenticated and network-reachable, but blind, limiting direct data theft while still enabling internal probing or request triggering.
Researcher notes
Key uncertainty is patch timing: sources say the issue is remediated but unclear when the fix was introduced. Validate version state before testing, and avoid assuming response visibility because the SSRF is described as blind.
Mitigation direction
- Upgrade Virtual Appliance Host to version 25.1.102 or later.
- Upgrade Print Application to version 25.1.1413 or later.
- Review current Vasion and PrinterLogic security bulletins for deployment-specific guidance.
- Restrict external access to affected management surfaces where operationally possible.
- Monitor unusual server-side outbound HTTP requests from Vasion Print systems.
Validation and detection
- Identify whether the deployment is VA, SaaS, or both.
- Confirm installed VA Host and Print Application versions.
- Check whether the affected PHP path is externally reachable.
- Review printer host address records for unexpected internal or attacker-controlled values.
- Inspect outbound logs for unusual requests to internal network destinations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCWE-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.
Open ATT&CK lookupCloud metadata behavior lookup
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.
Open ATT&CK lookupCVE-2025-34230 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.9MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://pierrekim.github.io/blog/2025-04-08-vasion-printerlogic-83-vulnerabilities.html#va-ssrf-06CVE reference, VulnCheck · technical-description
- https://help.printerlogic.com/va/Print/Security/Security-Bulletins.htmCVE reference, VulnCheck · vendor-advisory, patch
- https://help.printerlogic.com/saas/Print/Security/Security-Bulletins.htmCVE reference, VulnCheck · vendor-advisory, patch
- https://www.vulncheck.com/advisories/vasion-print-printerlogic-ssrf-via-hp-log-off-single-sign-on-php-scriptCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.