vciy

CVE-2025-34211

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Vasion Print (formerly PrinterLogic) Hardcoded SSL Certificate and Private Keys

CVE-2025-342114 of 4 sources documented this
16

rank 16 = 0 + 12 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00393  ·  without this subject the record ranks 16

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 4.9, from NVD  ·  without this subject the record ranks 4

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 16

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 12

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 16

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$18,200over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$18,200 = $4.99M incident cost x 0.9280467328949208 exposure x 0.00393 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00393EPSSNOT IN KEVas of 2026-09-20
Severity9.3 CRITICALreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-09-30, 334 days at 0.00, as of 2026-08-30. arc-rules@v1

Foresight · where to check next

GladinetCVE-2016-443734211

This record is one instance of CWE-321, use of hard-coded cryptographic key. The index holds 364 prior instances of this class, 2 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Severity score
VulnCheck9.3 CRITICALreceipt
NVD4.9 MEDIUMreceipt
Scoring standard
VulnCheckCVSS v4.0receipt
NVDCVSS v3.1receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running Vasion Print Virtual Appliance Host? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · high privileges required · no user interaction · low attack complexity · no attack requirementsreceipt
ImpactComplete confidentiality and integrity loss; partial availability loss, with impact on subsequent systemsreceipt
Scored fromCVSS v4.0 · the CNA's vectorreceipt
Weakness classCWE-321 Use of Hard-coded Cryptographic Keyreceipt
Published consequencesCWE-321: Access Control: Bypass Protection Mechanism, Gain Privileges or Assume Identity, Read Application Data[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in22.0.1049; 20.0.2786receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA9.3 CRITICALreceipt
CVSS, NVD4.9 MEDIUMreceipt
Exploit probability0.00393 · top 67% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned byVulnCheckreceipt
Recorded changes17 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productVasion Print Virtual Appliance Host; Vasion Print Applicationreceipt
Published rangesvasion virtual appliance application < 20.0.2786; vasion virtual appliance host < 22.0.1049receipt
Fixed in22.0.1049; 20.0.2786receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 22.0.1049 and Application prior to version 20.0.2786 (VA and SaaS deployments) contain a private SSL key and matching public certificate stored in cleartext. The key belongs to the hostname `pl‑local.com` and is used by the appliance to terminate TLS connections on ports 80/443. Because the key is hardcoded, any attacker who can gain container-level access can simply read the files and obtain the private key. receipt

Read the rest of the CNA's description

With the private key, the attacker can decrypt TLS traffic, perform man-in-the-middle attacks, or forge TLS certificates. This enables impersonation of the appliance’s web UI, interception of credentials, and unrestricted access to any services that trust the certificate. The same key is identical across all deployed appliances meaning a single theft compromises the confidentiality of every Vasion Print installation. This vulnerability has been identified by the vendor as: V-2024-025 — Hardcoded SSL Certificate & Private Keys.

NVD's analysis a second authority

severity
4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
weakness
CWE-321
affected versions
vasion virtual appliance application < 20.0.2786; vasion virtual appliance host < 22.0.1049
also scored by
[email protected] 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

The CNA scored it 9.3 and NVD 4.9. Both are shown because both were published; we do not pick one.

check it yourself pierrekim.github.io help.printerlogic.com help.printerlogic.com vulncheck.com receipt

Movement the material steps

30 Sep 20250.0002
15 Jun 20260.00359 · scoring model v2026.06.15
30 Aug 20260.00393
Show all 17 observations
30 Sep 20250.0002
4 Oct 20250.00013
5 Oct 20250.00016
31 Oct 20250.00018
10 Nov 20250.00024
6 Dec 20250.00025
29 Jan 20260.00031
25 Feb 20260.00023
26 Feb 20260.00022
9 Mar 20260.00029
12 Apr 20260.00045
25 Apr 20260.00051
5 May 20260.00049
4 Jun 20260.00053
15 Jun 20260.00359
25 Jun 20260.00367
30 Aug 20260.00393

17 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00393Published2025-09-29Index as of2026-08-30

The record had been public for 11 months when this index was last written.

Published 2025-09-29 receipt · Index as of 2026-08-30 derived

The pattern, elsewhere

This record is one instance of CWE-321, use of hard-coded cryptographic key. The index holds 364 prior instances of this class, 2 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2025-30406 · Gladinet CentreStackonly 1 attribute comparableKEV listed · 2025receipt
CVE-2016-4437nothing comparable heldKEV listed · 2016receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

364 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

vasion print virtual appliance host

Of the 3 records in this family, this is the only one holding a stated fix version: 22.0.1049; 20.0.2786.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2025-34211.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.