dbcve.org
WindriverApplication · Jungo

CVE-2023-51777

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
Denial of Service (DoS) vulnerability in Jungo WinDriver before 12.1.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 kernel-mode driver before version 12.1.0 allows local attackers to cause a Windows blue screen of death (BSOD), likely through improper IOCTL request handling or memory corruption in the kernel driver.

MitigationUpdate WinDriver to version 12.1.0 or later to patch the vulnerability; this is a kernel-level driver fix that requires applying the vendor's security update.

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 the Jungo WinDriver kernel driver
    Search the system for files named 'windriver.sys' or 'windrvr.sys' in driver directories (e.g., C:\Windows\System32\drivers\) or in program folders where Jungo WinDriver is typically installed
    Affected if The driver file exists on the system
  2. Determine the installed WinDriver version
    Right-click the WinDriver driver file and select Properties, then check the Version tab; or run 'windriver -v' from the WinDriver installation directory if a command-line tool exists
    Affected if The version displayed is earlier than 12.1.0
  3. Check for affected Mitsubishi applications
    Open Programs and Features (Windows) or check the installation directory for the following products: 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 (they bundle the vulnerable WinDriver driver)
  4. Verify the kernel driver is loaded
    Open Device Manager, enable 'Show hidden devices' in the View menu, and look for a device named 'WinDriver' under System devices or check driver status via 'sc query windrvr' in Command Prompt
    Affected if The WinDriver kernel driver is currently loaded or running on the system

You are affected if WinDriver kernel driver version is below 12.1.0, or if any of the listed Mitsubishi applications that bundle WinDriver are installed 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 to patch the vulnerability; this is a kernel-level driver fix that requires applying the vendor's security update.

Recommended fix High confidence

Windriver 12.1.0

  1. Identify all systems with Jungo WinDriver installed across the environment
  2. Check the current version of WinDriver on each system (versions prior to 12.1.0 are vulnerable)
  3. Download WinDriver version 12.1.0 or later from the official Jungo website or authorized distribution channel
  4. Upgrade WinDriver to version 12.1.0 on all affected systems
  5. Verify the upgrade was successful by checking the installed version number
  6. Test that the system no longer exhibits the blue screen behavior under the same conditions that would trigger the vulnerability

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

Fix this in Windriver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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