dbcve.org
Virtual Appliance ApplicationApplication · Vasion

CVE-2025-34206

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vasion Print (formerly PrinterLogic) Virtual Appliance Host and Application (VA and SaaS deployments) mount host configuration and secret material under /var/www/efs_storage into many Docker containers with overly-permissive filesystem permissions. Files such as secrets.env, GPG-encrypted blobs in .secrets, MySQL client keys, and application session files are accessible from multiple containers. An attacker who controls or reaches any container can read or modify these artifacts, leading to credential theft, RCE via Laravel APP_KEY, Portainer takeover, and full compromise.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Vasion Print Virtual Appliance mounts sensitive configuration and secret files from /var/www/efs_storage into multiple Docker containers with overly-permissive permissions, allowing any compromised container to read secrets.env, GPG blobs, MySQL keys, and session files, leading to credential theft and full system compromise.

MitigationRestrict filesystem permissions on mounted secrets/config files to enforce least-privilege access per container, implement proper secret isolation, rotate all exposed credentials (including Laravel APP_KEY and database credentials), and review container network segmentation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Virtual Appliance ApplicationApplication
Affected:all versions
Virtual Appliance HostApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Vasion Virtual Appliance installation
    Check if the system is running Vasion Print Virtual Appliance by examining /etc/os-release, hostname, or running 'docker ps' to list containers with 'vasion' or 'print' in names
    Affected if The system is confirmed to be a Vasion Virtual Appliance (Application or Host)
  2. Locate sensitive file mount directory
    Verify the existence of /var/www/efs_storage directory on the appliance host or within containers: run 'ls -la /var/www/efs_storage' on host or 'docker exec <container> ls -la /var/www/efs_storage' inside containers
    Affected if The /var/www/efs_storage directory exists and contains configuration files
  3. Check secrets.env file permissions
    Run 'ls -la' on secrets.env within /var/www/efs_storage or search for it: 'find /var/www/efs_storage -name secrets.env -exec ls -la {} \;'
    Affected if secrets.env file is readable by all users (permissions show 'world-readable' or 'other' has 'r' permission, such as 644 or more permissive)
  4. Inspect GPG blob and MySQL key file permissions
    Search for GPG files and MySQL key files in /var/www/efs_storage: 'find /var/www/efs_storage -name '*.gpg' -o -name '*mysql*' -o -name '*key*' | xargs ls -la 2>/dev/null'
    Affected if GPG blobs or MySQL keys are readable by all users (world-readable permissions)
  5. Verify Docker container mount access
    Examine Docker container mounts: run 'docker inspect <container> --format '{{.Mounts}}'' for each container and check if /var/www/efs_storage is mounted with readable permissions for the container user
    Affected if Containers have /var/www/efs_storage mounted and can read sensitive files without restriction

If this is a Vasion Virtual Appliance with /var/www/efs_storage containing secrets.env, GPG blobs, or MySQL keys that are world-readable or accessible to all containers, the environment is affected by CVE-2025-34206.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict filesystem permissions on mounted secrets/config files to enforce least-privilege access per container, implement proper secret isolation, rotate all exposed credentials (including Laravel APP_KEY and database credentials), and review container network segmentation.

Fix this in Virtual Appliance Application Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,960
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34206 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data