Security Resilience

CVE-2024-22105

Jungo Windriver ≤ 12.5.1

Published
02 July 2024
Modified
13 March 2025
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0020 9th percentile
Risk Priority 41 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-22105 is a medium-severity Improper Resource Shutdown or Release (CWE-404) vulnerability in Jungo Windriver. Its CVSS base score is 5.5 (Medium).

Operationally, ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Denial of Service (DoS) vulnerability in Jungo WinDriver before 12.5.1 allows local attackers to cause a Windows blue screen error.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-25087Same product: Jungo Windriver
CVE-2024-22104Same product: Jungo Windriver
CVE-2023-51776Same product: Jungo Windriver
CVE-2024-22106Same product: Jungo Windriver
CVE-2024-22103Same product: Jungo Windriver
CVE-2024-22102Same product: Jungo Windriver
CVE-2024-25088Same product: Jungo Windriver
CVE-2024-25086Same product: Jungo Windriver
CVE-2024-26314Same product: Jungo Windriver
CVE-2023-51778Same product: Jungo Windriver

Affected Assets

jungo
windriver
≤ 12.5.1
mitsubishielectric
cpu module logging configuration tool
all versions
mitsubishielectric
cw configurator
all versions
mitsubishielectric
data transfer
all versions
mitsubishielectric
data transfer classic
all versions
mitsubishielectric
ezsocket
all versions
mitsubishielectric
fr configurator sw3
all versions
mitsubishielectric
fr configurator2
all versions
mitsubishielectric
genesis64
all versions
mitsubishielectric
gt got1000
all versions
+25 more product configuration(s) — see NVD for full list

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect resource releases after code is written.

Engineering principles can require explicit resource acquisition/release patterns that stop improper shutdown from being introduced.

Priority-based resource allocation limits the blast radius when released resources are not returned to the pool.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

documenting procedures for secure operation, error handling, restart/recovery and resource management (including references to 8.13/8.18) is a governance and dependency control that does not itself stop exploitation of a resource-shutdown flaw; any prevention would require other controls (e.g. code changes or runtime enforcement) configured to act on it

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-404, a class-level weakness, and none of its children carries one either.

References