Security readout for executives and security teams
Plain-English summary
Vasion Print exposed a group-search API without authentication in affected VA and SaaS deployments. An outside attacker could learn internal group metadata for a tenant. This is an information disclosure issue, not direct code execution, but it can support reconnaissance against identity and print-management environments.
Executive priority
Treat as a near-term remediation item for Vasion Print environments. It does not indicate system takeover, but it exposes identity structure useful to attackers preparing targeted follow-on activity.
Technical view
CVE-2025-34220 is a CWE-306/CWE-200 flaw in /api-gateway/identity/search-groups. Affected versions are Virtual Appliance Host before 25.1.102 and Application before 25.1.1413. Unauthenticated remote requests could enumerate tenant group objects and identifiers, including Azure AD object IDs, source service IDs, timestamps, and tenant IDs.
Likely exposure
Organizations using Vasion Print or former PrinterLogic VA/SaaS deployments before the named fixed versions are the likely exposure group, especially internet-reachable tenant environments.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. The issue is remotely reachable and unauthenticated, so it is plausible for reconnaissance if the affected tenant endpoint is exposed.
Researcher notes
CVSS v4.0 score is 6.9 with network, low-complexity, no-privilege, no-user-interaction conditions and low confidentiality impact. The source bundle says remediation is confirmed, but the exact patch introduction timing is unclear.
Mitigation direction
- Upgrade VA Host to 25.1.102 or later where applicable.
- Upgrade Print Application to 25.1.1413 or later where applicable.
- Review Vasion security bulletins for deployment-specific guidance.
- Restrict unauthenticated internet access to management and identity APIs where possible.
- Monitor for unexpected unauthenticated identity or group-search activity.
Validation and detection
- Inventory Vasion Print VA and SaaS tenants and record component versions.
- Confirm affected deployments are at or beyond the fixed versions.
- Verify group-search APIs require authentication from untrusted networks.
- Review access logs for anonymous requests to identity group-search paths.
- Check vendor advisories for any later remediation notes.
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-200: 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 lookupCWE-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 lookupCVE-2025-34220 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:N/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:N/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:N/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-api-leakCVE 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-unauth-api-leaks-group-infoCVE 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.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.