dbcve.org
WindriverApplication · Jungo

CVE-2023-51778

MEDIUM · 5.5 CVSS v3.1 Published 2024-07-02
Fix available
A fix is available. Upgrade to 12.1.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
Out-of-Bounds Write vulnerability in Jungo WinDriver before 12.1.0 allows local attackers to cause a Windows blue screen error and 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 · high confidence

An out-of-bounds write vulnerability exists in Jungo WinDriver versions prior to 12.1.0. Local attackers can exploit this flaw to write data beyond allocated memory boundaries, triggering a Windows blue screen (BSOD) and causing a complete system crash and Denial of Service.

MitigationUpdate WinDriver to version 12.1.0 or later. If immediate patching is not feasible, restrict local access to systems with WinDriver installed and monitor for suspicious driver-level operations.

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.1.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 installation
    Check for WinDriver in common installation directories such as C:\Program Files\Jungo\WinDriver, C:\Program Files (x86)\Jungo\WinDriver, or search for 'windriver' folder on the system. Also check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Jungo or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Jungo for WinDriver entries.
    Affected if WinDriver is found installed on the system.
  2. Identify WinDriver version
    Right-click the WinDriver driver file (typically windriver.sys or wdapi*.sys in the driver directory) and select Properties, then check the Details tab for the File Version. Alternatively, check the version in the Windows Registry under the WinDriver registry key.
    Affected if The installed version is any version prior to 12.1.0, or if the version cannot be determined but WinDriver is present.
  3. Check for vulnerable Mitsubishi products
    Search for and list installed programs matching any of these: CPU Module Logging Configuration Tool, CW Configurator, Data Transfer, Data Transfer Classic, Ezsocket, FR Configurator SW3, or FR Configurator2. Check in Add/Remove Programs or search for these program directories under C:\Program Files or C:\Program Files (x86).
    Affected if Any of these Mitsubishi Electric products are installed (all versions are affected according to the CVE).
  4. Verify WinDriver driver is loaded
    Open Device Manager, select 'Show hidden devices', and look for Jungo WinDriver devices under System devices or check driver status via 'sc query windriver' command in an elevated command prompt.
    Affected if The WinDriver kernel driver is loaded or running on the system.

The system is affected if Jungo WinDriver with a version below 12.1.0 is installed, or if any of the vulnerable Mitsubishi Electric products (CPU Module Logging Configuration Tool, CW Configurator, Data Transfer, Data Transfer Classic, Ezsocket, FR Configurator SW3, or FR Configurator2) 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.1.0 or later
Fixed in 12.1.0
Interim mitigation

Update WinDriver to version 12.1.0 or later. If immediate patching is not feasible, restrict local access to systems with WinDriver installed and monitor for suspicious driver-level operations.

Recommended fix High confidence

Jungo WinDriver 12.1.0 or later

  1. Identify all systems with Jungo WinDriver installed
  2. Verify current WinDriver version by checking the Jungo WinDriver installation directory or using the version information in the driver properties
  3. Download Jungo WinDriver version 12.1.0 or later from the official Jungo website or your vendor's software distribution channel
  4. Back up any existing WinDriver configurations, scripts, or custom files
  5. Uninstall the current version of WinDriver from affected systems
  6. Install WinDriver version 12.1.0 or later on all affected systems
  7. Restore any backed-up configurations after installation
  8. Reboot the systems to ensure the new driver loads properly
Caveat Review release notes for version 12.1.0 for any API changes or driver behavior modifications that may affect existing software using WinDriver

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

Fix this in Windriver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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