WindriverApplication · Jungo

CVE-2024-22106

HIGH · 7.8 CVSS v3.1 Published 2024-07-02
Fix available
A fix is available. Upgrade to 12.5.1 or later.
See remediation →
80/100
Remediation priority · High
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
Improper privilege management in Jungo WinDriver before 12.5.1 allows local attackers to escalate privileges, execute arbitrary code, or cause a Denial of Service (DoS).

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 · moderate confidence

Jungo WinDriver before version 12.5.1 contains improper privilege management that allows local attackers to escalate privileges to execute arbitrary code or cause denial of service. This is a local privilege escalation vulnerability affecting the driver software.

MitigationUpgrade Jungo WinDriver to version 12.5.1 or later to remediate this vulnerability. As this is a driver component, verify functionality after deployment.

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
WindriverApplication
Affected:< 12.5.1
Cpu Module Logging Configuration ToolPlugin / extension
Affected:all versions
Cw ConfiguratorApplication
Affected:all versions
Data TransferApplication
Affected:all versions
Data Transfer ClassicApplication
Affected:all versions
EzsocketApplication
Affected:all versions
Fr Configurator Sw3Application
Affected:all versions
Fr Configurator2Application
Affected:all versions

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Find Jungo WinDriver installation directory
    Search for 'windriver' or 'WinDriver' folders in common installation paths such as C:\Jungo, C:\Program Files\Jungo, or C:\Program Files (x86)\Jungo. Also check the Windows\System32\drivers folder for windriver.sys or similar driver files.
    Affected if WinDriver directory or driver files exist on the system
  2. Check WinDriver version
    Locate the WinDriver version information file (typically version.ini, about.dll, or the main executable in the WinDriver folder). Right-click the file, select Properties, and view the Version tab to identify the product version.
    Affected if Installed version is lower than 12.5.1 or version cannot be determined (treat unknown as potentially vulnerable)
  3. Verify driver is loaded or loadable
    Open Command Prompt as administrator and run 'sc query windriver' or check Device Manager under 'Jungo WinDriver' devices. Also check for driver services using 'sc enumdepend' or review the driver file properties.
    Affected if WinDriver service or device exists and version is below 12.5.1
  4. Identify bundled Mitsubishi applications
    Check for installed Mitsubishi software that may bundle WinDriver. Look in Add/Remove Programs (appwiz.cpl) or the installation directories of: CPU Module Logging Configuration Tool, CW Configurator, Data Transfer, Data Transfer Classic, Ezsocket, FR Configurator SW3, or FR Configurator2.
    Affected if Any of these Mitsubishi applications are installed (all versions are affected per the CVE)
  5. Review driver file permissions
    Locate the windriver.sys file (typically in Windows\System32\drivers or the Jungo installation folder). Right-click the file, go to Security tab, and verify which users or groups have Write or Full Control permissions.
    Affected if Non-admin users have write access to driver files or configuration (indicates the privilege escalation condition exists)

The environment is affected if Jungo WinDriver version is present and is lower than 12.5.1, or if any listed Mitsubishi applications that bundle WinDriver are installed (regardless of version).

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 12.5.1 or later
Fixed in 12.5.1
Interim mitigation

Upgrade Jungo WinDriver to version 12.5.1 or later to remediate this vulnerability. As this is a driver component, verify functionality after deployment.

Recommended fix High confidence

12.5.1

  1. Identify all systems and applications using Jungo WinDriver (versions prior to 12.5.1)
  2. Obtain Jungo WinDriver version 12.5.1 or later from the official Jungo vendor
  3. Backup all critical data and configurations before performing the upgrade
  4. Upgrade Jungo WinDriver to version 12.5.1 or later on all affected systems
  5. Verify the upgrade was successful by checking the WinDriver version
  6. Test that affected applications (Cpu Module Logging Configuration Tool, Cw Configurator, Data Transfer, Data Transfer Classic, Ezsocket, Fr Configurator Sw3, Fr Configurator2) function correctly post-upgrade
  7. Apply security updates or patches for any third-party applications that bundle the vulnerable WinDriver component

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

Fix this in Windriver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22106 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22106 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