dbcve.org
WindriverApplication · Jungo

CVE-2024-25087

MEDIUM · 5.5 CVSS v3.1 Published 2024-07-02
Fix available
A fix is available. Upgrade to 12.7.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Denial of Service (DoS) vulnerability in Jungo WinDriver before 12.7.0 allows local attackers to cause a Windows blue screen error.

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

A local denial-of-service vulnerability in Jungo WinDriver versions before 12.7.0 allows local attackers to trigger a Windows blue screen error (bugcheck), likely due to improper driver handling causing a kernel-mode crash.

MitigationUpgrade Jungo WinDriver to version 12.7.0 or later to remediate the vulnerability.

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.7.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Locate Jungo WinDriver kernel driver files
    Search for WinDriver kernel files in the Windows system directory. Common paths: C:\Windows\System32\drivers\wd*.sys or C:\Windows\SysWOW64\drivers\wd*.sys (32-bit driver on 64-bit system). Use PowerShell command: Get-ChildItem -Path $env:SystemRoot\System32\drivers -Filter "wd*.sys" -ErrorAction SilentlyContinue
    Affected if If any wd*.sys driver files exist from Jungo WinDriver, the system may be affected if the version is below 12.7.0
  2. Check the driver file version
    Right-click each wd*.sys file found, select Properties, then view the Details tab for the Product Version, or use PowerShell: (Get-Item "C:\Windows\System32\drivers\wd_driver.sys").VersionInfo | Select-Object ProductVersion, FileVersion
    Affected if If the product version is present and is less than 12.7.0, the system is vulnerable to CVE-2024-25087
  3. Identify installed Jungo WinDriver software via registry
    Check Windows Registry for Jungo WinDriver installation. Query: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* or HKLM\SOFTWARE\Jungo\WinDriver. Use PowerShell: Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*" | Where-Object {$_.Publisher -like "*Jungo*"}
    Affected if If Jungo WinDriver is listed as installed and the version shown is below 12.7.0, the environment is affected
  4. Check for Mitsubishi product installations that bundle WinDriver
    If the system has any Mitsubishi Electric products listed in the affected products (Cpu Module Logging Configuration Tool, CW Configurator, Data Transfer, Ezsocket, FR Configurator, FR Configurator2), check their installation directories for bundled wd*.sys drivers. Common paths: C:\Program Files\MitsubishiElectric\* or product-specific directories.
    Affected if If any Mitsubishi Electric product from the affected list is installed and contains a bundled wd*.sys driver version below 12.7.0, the system is vulnerable

A system is affected if any Jungo WinDriver driver (wd*.sys) with version below 12.7.0 is present on the system, either as standalone software or bundled with Mitsubishi Electric products, as this allows local attackers to trigger a kernel-mode crash (blue screen).

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.

From vendor data
Upgrade available Upgrade to 12.7.0 or later
Fixed in 12.7.0
Interim mitigation

Upgrade Jungo WinDriver to version 12.7.0 or later to remediate the vulnerability.

Fix this in Windriver Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $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 $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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