dbcve.org
WindriverApplication · Jungo

CVE-2024-25086

HIGH · 7.8 CVSS v3.1 Published 2024-07-02
Fix available
A fix is available. Upgrade to 12.2.0 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.2.0 allows local attackers to escalate privileges and execute arbitrary code.

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

This is a local privilege escalation vulnerability in Jungo WinDriver. The 'improper privilege management' flaw allows a local attacker to elevate their privileges beyond what they should have and execute arbitrary code with those elevated privileges.

MitigationUpgrade to Jungo WinDriver version 12.2.0 or later. As this is a local privilege escalation with CVSS 7.8, prioritize patching for systems where untrusted local users have access.

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.2.0
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 and version
    Check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Jungo' or 'WinDriver', or inspect the typical installation path (C:\Jungo\WinDriver) if it exists. Look for a version number in the uninstall entry or version file.
    Affected if Jungo WinDriver is found with a version lower than 12.2.0, or if the version cannot be determined and the software is present.
  2. Find Mitsubishi Electric affected products
    Check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing any of these names: 'Cpu Module Logging Configuration Tool', 'Cw Configurator', 'Data Transfer', 'Ezsocket', 'Fr Configurator Sw3', 'Fr Configurator2'. Also check the Mitsubishi program directory under Program Files.
    Affected if Any of the listed Mitsubishi Electric products are found installed on the system.
  3. Locate WinDriver privilege escalation component
    Search for the WinDriver driver files or the wdreg.exe utility (commonly found in C:\Jungo\WinDriver\tools or C:\Jungo\WinDriver\bin) which handles driver installation with elevated privileges.
    Affected if The WinDriver components (driver files, wdreg.exe, or kernel driver service) are present on the system.
  4. Verify driver service exists
    Open Services (services.msc) and look for any service named 'WinDriver' or similar Jungo-related driver services that run with elevated system privileges.
    Affected if A WinDriver-related service is installed and running on the system.

The system is affected if Jungo WinDriver (any version below 12.2.0) or any of the Mitsubishi Electric products (Cpu Module Logging Configuration Tool, Cw Configurator, Data Transfer, Ezsocket, Fr Configurator variants) are present on the system.

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.2.0 or later
Fixed in 12.2.0
Interim mitigation

Upgrade to Jungo WinDriver version 12.2.0 or later. As this is a local privilege escalation with CVSS 7.8, prioritize patching for systems where untrusted local users have access.

Recommended fix High confidence

Windriver 12.2.0 or later (Jungo WinDriver 12.2.0)

  1. 1. Identify all systems with Jungo WinDriver installed by checking the driver version (typically in C:\Windows\System32\drivers\windrvr*.sys or via the WinDriver version utility)
  2. 2. Download WinDriver version 12.2.0 or later from the official Jungo website (jungo.com) or your vendor's patched distribution
  3. 3. Back up all current WinDriver configurations, custom driver projects, and license files
  4. 4. Stop any running applications that use WinDriver (including the affected products: Cpu Module Logging Configuration Tool, Cw Configurator, Data Transfer, Data Transfer Classic, Ezsocket, Fr Configurator Sw3, Fr Configurator2)
  5. 5. Uninstall the existing WinDriver version via the vendor's recommended removal procedure
  6. 6. Install the new WinDriver 12.2.0 or later version
  7. 7. Restore configurations and re-register any license files if required
  8. 8. Restart the previously stopped applications and verify they function correctly
Caveat Review vendor release notes for any API changes between your current version and 12.2.0 that may affect custom driver code or integrated applications; test in a staging environment before production deployment

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

Fix this in Windriver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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