{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-34201 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-34201 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-34201 is a high-severity vulnerability in Vasion Print Application, published on 19 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-34201 and fix it if it is affected.\n\nWhat it is: CVE-2025-34201 is a high-severity vulnerability in Vasion Print Application, published on 19 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-34201 in the wild and no public exploit code.\n\nAffected product: Vasion Print Application. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-34201/ (Markdown: https://insights.sbomify.com/CVE-2025-34201/index.md)","id":"CVE-2025-34201","markdown":"https://insights.sbomify.com/CVE-2025-34201/index.md","name":"CVE-2025-34201","record":{"aliases":["GHSA-3qpr-9m66-7297"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"configuration_change","impacts":["privilege_escalation","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vasion Print Appliance","requires_auth":"low_privilege","summary":"Lack of network segmentation in Vasion Print Docker containers allows attackers to move laterally and access internal services after compromising a single container.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"virtual_appliance_application","vendor":"vasion"},{"product":"virtual_appliance_host","vendor":"vasion"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-653","name":"Improper Isolation or Compartmentalization"}],"description":"Vasion Print (formerly PrinterLogic) Virtual Appliance Host and Application (VA and SaaS deployments) run many Docker containers on shared internal networks without firewalling or segmentation between instances. A compromise of any single container allows direct access to internal services (HTTP, Redis, MySQL, etc.) on the overlay network. From a compromised container, an attacker can reach and exploit other services, enabling lateral movement, data theft, and system-wide compromise.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Vasion Print (formerly PrinterLogic) Lack of Network Segmentation Between Docker Instances","id":"CVE-2025-34201","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Vasion Print (formerly PrinterLogic) Insecure Access to Docker Instances WAN","id":"CVE-2025-34202"},"packages":[],"prev":{"headline":"Vasion Print (formerly PrinterLogic) Network Account Password Stored in Cleartext","id":"CVE-2025-34200"},"products":["Print Application","Print Virtual Appliance Host"],"published":"2025-09-19","related":[{"cvss_score":10,"headline":"Vasion Print (formerly PrinterLogic) Undocumented Hardcoded SSH Key","id":"CVE-2025-34217","kev_date_added":null,"published":"2025-09-30"},{"cvss_score":10,"headline":"Vasion Print (formerly PrinterLogic) RCE and Password Leaks via API","id":"CVE-2025-34216","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":10,"headline":"Vasion Print (formerly PrinterLogic) Exposed Internal Docker Instance","id":"CVE-2025-34218","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":10,"headline":"Vasion Print (formerly PrinterLogic)","id":"CVE-2025-34221","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":10,"headline":"Vasion Print (formerly PrinterLogic) Unauthenticated Admin APIs Used to Modify SSL Certificates","id":"CVE-2025-34222","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":10,"headline":"Vasion Print (formerly PrinterLogic) Insecure Installation Credentials","id":"CVE-2025-34223","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":10,"headline":"Vasion Print (formerly PrinterLogic) Unauthenticated Device Modification","id":"CVE-2025-34224","kev_date_added":null,"published":"2025-09-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-17","vendors":["Vasion"]},"summary":"Lack of network segmentation in Vasion Print Docker containers allows attackers to move laterally and access internal services after compromising a single container.","url":"https://insights.sbomify.com/CVE-2025-34201/"}