dbcve.org
Virtual Appliance ApplicationApplication · Vasion

CVE-2025-34212

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 20.0.1923 / 22.0.843 or later.
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 prior to version 22.0.843 and Application prior to version 20.0.1923 (VA/SaaS deployments) possess CI/CD weaknesses: the build pulls an unverified third-party image, downloads the VirtualBox Extension Pack over plain HTTP without signature validation, and grants the jenkins account NOPASSWD for mount/umount. Together these allow supply chain or man-in-the-middle compromise of the build pipeline, injection of malicious firmware, and remote code execution as root on the CI host. This vulnerability has been identified by the vendor as: V-2023-007 — Supply Chain Attack.

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 contains critical CI/CD supply chain vulnerabilities: builds pull unverified third-party images, download VirtualBox Extension Pack over plain HTTP without signature validation, and the jenkins account has NOPASSWD sudo access for mount/umount. These weaknesses enable MITM attacks to inject malicious firmware and achieve root RCE on the CI host.

MitigationUpgrade to version 22.0.843 (VA) or 20.0.1923 (Application), implement image signature verification, enforce HTTPS with signature validation for all downloads, and remove NOPASSWD sudo rules for the jenkins account.

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:< 20.0.1923
Virtual Appliance HostApplication
Affected:< 22.0.843

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. Check Vasion Virtual Appliance Application version
    Run 'rpm -q vasion' or check the application version through the admin interface under System > About
    Affected if version is lower than 20.0.1923
  2. Check Vasion Virtual Appliance Host version
    Run 'hostnamectl' or check the underlying host system version, or look for VA version in the virtualization environment
    Affected if host version is lower than 22.0.843
  3. Verify jenkins sudo configuration
    Run 'sudo -l -U jenkins' and examine the output for NOPASSWD rules, or inspect /etc/sudoers and /etc/sudoers.d/ for 'jenkins' entries with NOPASSWD
    Affected if jenkins user has NOPASSWD sudo access for mount or umount commands
  4. Check CI/CD build configuration for image pull settings
    Inspect CI/CD pipeline configuration files (Jenkinsfile, GitLab CI YAML, or similar) for docker pull or image deployment commands and verify if signature verification is implemented
    Affected if builds pull images without signature validation or from untrusted sources
  5. Check for plain HTTP downloads in build or deployment scripts
    Search build scripts, deployment playbooks, and automation files for HTTP URLs (not HTTPS) related to VirtualBox Extension Pack or third-party software downloads
    Affected if VirtualBox Extension Pack or other software is downloaded over HTTP without signature validation

Environment is affected if running Vasion Virtual Appliance Application below 20.0.1923 or Host below 22.0.843, AND the jenkins account has NOPASSWD sudo rules, AND builds pull unverified images or download software over plain HTTP.

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.1923 / 22.0.843 or later
Fixed in 20.0.192322.0.843
Interim mitigation

Upgrade to version 22.0.843 (VA) or 20.0.1923 (Application), implement image signature verification, enforce HTTPS with signature validation for all downloads, and remove NOPASSWD sudo rules for the jenkins account.

Recommended fix High confidence

Virtual Appliance Application: 20.0.1923 or later; Virtual Appliance Host: 22.0.843 or later

  1. Identify the current version of Virtual Appliance Application and Virtual Appliance Host currently deployed
  2. Upgrade the Virtual Appliance Application to version 20.0.1923 or later
  3. Upgrade the Virtual Appliance Host to version 22.0.843 or later
  4. After upgrading, verify that the CI/CD build pipeline no longer pulls unverified third-party images
  5. Verify that VirtualBox Extension Pack downloads now use secure channels with signature validation
  6. Confirm the jenkins account NOPASSWD permissions for mount/umount have been removed or properly restricted

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

Fix this in Virtual Appliance Application Scoped from the published advisory
  • Consultation10.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
46.0 hours of engineering $8,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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