CVE-2024-22103
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 · uneditedOut-of-Bounds Write vulnerability in Jungo WinDriver before 12.6.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 confidenceAn out-of-bounds write vulnerability in Jungo WinDriver before version 12.6.0 allows local attackers to write beyond allocated memory boundaries, triggering a Windows blue screen (BSOD) crash and causing denial of service.
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< 12.6.0all versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Jungo WinDriver versionLocate the WinDriver driver file (typically windrvr.sys or similar driver files in the Windows system32/drivers folder or Jungo installation directory) and check its file version property, or use 'driverquery /v' to list driver details.Affected if The installed WinDriver version is below 12.6.0 or the version cannot be determined (indicating an older vulnerable release).
-
Identify installed Mitsubishi productsCheck installed programs list (via Programs and Features or registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) for any of these: CPU Module Logging Configuration Tool, CW Configurator, Data Transfer, Data Transfer Classic, Ezsocket, FR Configurator SW3, or FR Configurator2.Affected if Any of the listed Mitsubishi products are installed, as they bundle the vulnerable Jungo WinDriver component in all versions.
-
Check for Jungo WinDriver serviceOpen Services console (services.msc) and look for a service named 'Windriver' or 'Jungo WinDriver', or run 'sc query windrvr' from command prompt to query the service status and version info.Affected if The Windriver service exists and its associated driver file version is below 12.6.0.
You are affected if Jungo WinDriver version is below 12.6.0, or if any of the listed Mitsubishi products (which bundle WinDriver) are installed on the system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.6.0
Upgrade Jungo WinDriver to version 12.6.0 or later to remediate the vulnerability.
WinDriver 12.6.0 or later
- 1. Identify the currently installed Jungo WinDriver version by checking the product documentation or using the vendor's version check utility
- 2. Navigate to the official Jungo WinDriver download page or contact Jungo/your product vendor to obtain version 12.6.0 or later
- 3. Review the vendor's upgrade documentation and release notes for any special installation requirements
- 4. Back up current system state and any existing WinDriver configurations before proceeding
- 5. Install WinDriver version 12.6.0 or later following the vendor's official installation procedures
- 6. Verify the installation was successful by confirming the new version number
- 7. Test that the target system boots and operates normally without blue screen errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22103 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22103 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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