dbcve.org
Vasion PrintApplication · Printerlogic

CVE-2025-27650

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-05
Fix available
A fix is available. Upgrade to 20.0.2014 / 22.0.862 or later.
See remediation →
100/100
Remediation priority · Urgent
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) before Virtual Appliance Host 22.0.862 Application 20.0.2014 allows Private Keys in Docker Overlay V-2023-013.

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 before version 22.0.862 (host) and 20.0.2014 (application) stores private cryptographic keys within the Docker overlay filesystem. This exposes sensitive key material that persists in container layers and can be extracted by attackers with container escape or host access, enabling authentication bypass or data decryption.

MitigationMigrate private keys to a proper secrets management solution (e.g., Docker Secrets, Kubernetes Secrets, HashiCorp Vault), regenerate all exposed keys, and ensure sensitive material is never stored in container images or overlay filesystems.

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
Vasion PrintApplication
Affected:< 20.0.2014
Virtual ApplianceApplication
Affected:< 22.0.862

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. Determine VA Host version
    Log into the Virtual Appliance and run: cat /etc/version or ls /opt/printnerlogic/version 2>/dev/null; alternatively, check the PrinterLogic admin panel for the Host version under System Maintenance or About section
    Affected if Version is below 22.0.862
  2. Determine Application version
    Log into the PrinterLogic admin panel and navigate to Administration > System Maintenance > About, or run: docker ps | grep -i app and inspect the container version tag
    Affected if Version is below 20.0.2014
  3. Inspect Docker overlay filesystem for private keys
    Run: docker info --format '{{ .DockerRootDir }}' to find the Docker data directory, then examine contents under /var/lib/docker/overlay2/ for .key, .pem, or private key files using find /var/lib/docker/overlay2 -type f \( -name "*.key" -o -name "*.pem" -o -name "*private*" \) 2>/dev/null
    Affected if Any private key files (.key, .pem) exist in Docker overlay directories
  4. Check for SSL/TLS certificate storage locations
    Examine common certificate directories inside Docker containers: ls -la /etc/ssl/private/ /opt/ PrinterLogic/ssl/ /var/opt/PrinterLogic/ssl/ 2>/dev/null inside the application container, or inspect mounted volumes
    Affected if Private certificates or keys are stored in application data directories accessible via Docker overlay
  5. Verify Docker filesystem access exposure
    Check if the Docker storage driver is overlay2: docker info --format '{{ .Driver }}'. If using overlay2, verify file permissions on /var/lib/docker/overlay2/ are not world-readable or accessible via container escape
    Affected if Docker uses overlay2 driver and overlay filesystem directories are accessible beyond intended container isolation

You are affected if either the VA Host version is below 22.0.862 or the Application version is below 20.0.2014, and private keys exist in Docker overlay filesystem locations on the appliance.

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.

dbcve · scoped
Upgrade available Upgrade to 20.0.2014 / 22.0.862 or later
Fixed in 20.0.201422.0.862
Interim mitigation

Migrate private keys to a proper secrets management solution (e.g., Docker Secrets, Kubernetes Secrets, HashiCorp Vault), regenerate all exposed keys, and ensure sensitive material is never stored in container images or overlay filesystems.

Recommended fix High confidence

Virtual Appliance Host 22.0.862 / Vasion Print Application 20.0.2014 or higher

  1. Backup current Vasion Print configuration and data
  2. Upgrade Virtual Appliance Host to version 22.0.862 or higher
  3. Upgrade Vasion Print Application to version 20.0.2014 or higher
  4. Verify the upgrade completed successfully by checking the version numbers in the admin console
  5. Confirm that private keys are no longer exposed in Docker overlay filesystem

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vasion Print Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27650 — 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-27650 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