CVE-2025-34192
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 · uneditedVasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 22.0.893 and Application versions prior to 20.0.2140 (macOS/Linux client deployments) are built against OpenSSL 1.0.2h-fips (released May 2016), which has been end-of-life since 2019 and is no longer supported by the OpenSSL project. Continued use of this outdated cryptographic library exposes deployments to known vulnerabilities that are no longer patched, weakening the overall security posture. Affected daemons may emit deprecation warnings and rely on cryptographic components with unresolved security flaws, potentially enabling attackers to exploit weaknesses in TLS/SSL processing or cryptographic operations. This vulnerability has been identified by the vendor as: V-2023-021 — Out-of-Date OpenSSL Library.
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 confidenceVasion Print Virtual Appliance Host and Application versions ship with OpenSSL 1.0.2h-fips, an OpenSSL branch that reached end-of-life in December 2019 and no longer receives security patches. This exposes deployments to all disclosed OpenSSL vulnerabilities since 2019, including weaknesses in TLS/SSL processing and cryptographic operations that will not be remediated by the OpenSSL project.
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< 20.0.2140< 22.0.893CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Vasion Virtual Appliance installationCheck if Vasion Print Virtual Appliance (either Host or Application) is installed in your environment. Look for the product in your software inventory, installed applications list, or check for Vasion-related processes and services.Affected if Vasion Virtual Appliance Host or Application is present on the system
-
Determine Virtual Appliance Application version (Linux/macOS client)For the Application component (Linux or macOS client), run the command to check the installed version - typically through the application's about dialog, version flag (--version), or by querying the installed package information using your system's package manager or the application's built-in version check.Affected if The Application version is found to be less than 20.0.2140
-
Determine Virtual Appliance Host versionFor the Virtual Appliance Host component, check the version through the appliance's administrative interface, system information page, or by querying the host's service/version information. This is typically accessible via the management console or system documentation.Affected if The Host version is found to be less than 22.0.893
-
Verify OpenSSL library version in useIf Vasion is installed, identify the OpenSSL library version being used by the Vasion components. This may require examining the OpenSSL libraries bundled with or used by the application, or running 'openssl version' if the vulnerable library is accessible system-wide.Affected if OpenSSL version 1.0.2h-fips or any 1.0.2 branch version is in use (OpenSSL 1.0.2 reached EOL in December 2019)
You are affected if Vasion Virtual Appliance Application is below version 20.0.2140 or Host is below version 22.0.893, indicating they ship with the unsupported OpenSSL 1.0.2 branch.
Generated from the published advisory. Verify against your own configuration.
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 · scoped20.0.214022.0.893
Upgrade Virtual Appliance Host to version 22.0.893 or later, and Application (macOS/Linux client) to version 20.0.2140 or later, to replace the unsupported OpenSSL library with a currently maintained version.
Virtual Appliance Application: 20.0.2140+ | Virtual Appliance Host: 22.0.893+
- 1. Identify which Vasion Print Virtual Appliance product is deployed (Application or Host)
- 2. For Virtual Appliance Application: Upgrade to version 20.0.2140 or later
- 3. For Virtual Appliance Host: Upgrade to version 22.0.893 or later
- 4. Verify the upgrade completed successfully and the OpenSSL library has been updated
- 5. Test critical printing workflows to ensure functionality is intact
- 6. Review release notes for any additional changes in the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-34192 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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