LiveActive security incident?Get immediate response
CVE Record

CVE-2025-34234: Vasion Print (formerly PrinterLogic) Hardcoded Encryption Private Keys

Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 25.1.102 and Application prior to version 25.1.1413 (VA/SaaS deployments) contain two hardcoded private keys that are shipped in the application containers (printerlogic/pi, printerlogic/printer-admin-api, and printercloud/pi). The keys are stored in clear text under /var/www/app/config/ as keyfile.ppk.dev and keyfile.saasid.ppk.dev. The application uses these keys as the symmetric secret for AES‑256‑CBC encryption/decryption of the “SaaS Id” (external identifier) through the getEncryptedExternalId() / getDecryptedExternalId() methods. Because the secret is embedded in the deployed image, any attacker who can obtain a copy of the Docker image, read the configuration files, or otherwise enumerate the filesystem can recover the encryption key. This vulnerability has been confirmed to be remediated, but it is unclear as to when the patch was introduced.

CriticalCVSS 9.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Vasion Print shipped private encryption keys inside application containers. If someone can obtain the image or read those files, they can recover the key used to encrypt and decrypt the SaaS external identifier. This is critical because the secret is shared by design, but the sources do not show active exploitation.

Executive priority

Treat this as urgent for any organization using Vasion Print. Prioritize version verification and upgrade because the weakness is embedded secret material, not a configuration mistake that administrators can reliably harden away.

Technical view

CVE-2025-34234 is CWE-321 in Vasion Print Virtual Appliance Host before 25.1.102 and Application before 25.1.1413. Hardcoded cleartext keys are stored under /var/www/app/config/ in listed containers and used as the AES-256-CBC secret for SaaS Id encryption/decryption methods.

Likely exposure

Exposure is most likely in Vasion Print VA or SaaS deployments running versions below the stated fixed thresholds, especially where container images, backups, registries, or appliance filesystems are accessible beyond tightly controlled administrators.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The described attack depends on obtaining the shipped key from an image or filesystem, then abusing knowledge of that secret; the sources do not provide broader exploit maturity evidence.

Researcher notes

Evidence is strong for the hardcoded-key condition and affected paths, but the bundle says remediation timing is unclear. Avoid assuming active exploitation, additional affected products, or key rotation behavior unless Vasion guidance confirms it.

Mitigation direction

  • Upgrade Vasion Print VA Host to 25.1.102 or later.
  • Upgrade Vasion Print Application to 25.1.1413 or later.
  • Check Vasion and PrinterLogic security bulletins for current remediation guidance.
  • Restrict access to container images, registries, backups, and appliance filesystems.
  • Review possible exposure of affected images or configuration backups.

Validation and detection

  • Inventory Vasion Print VA and SaaS deployments and record component versions.
  • Check for affected containers named in the advisory.
  • Confirm vulnerable key files are absent from current deployed images.
  • Review registry, backup, and filesystem access logs for unusual access.
  • Verify vendor bulletins show the deployment is on a remediated release.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-321: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-34234 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.2 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.2CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N——VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.2Critical
CVSS 4.0 vector shape for CVE-2025-34234Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
VasionPrint Virtual Appliance Host0unaffected
VasionPrint Application0unaffected
Weakness

CWE details

CWE-321

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-321 · source CWE mapping

Use of Hard-coded Cryptographic Key

Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs