Cyber Resilience

CVE-2024-26242

Race Condition in Microsoft Windows 10 1507 ≤ 10.0.10240.20596

Race Condition
Published
09 April 2024
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0035 27th percentile
Risk Priority 51 floored blend · peak EPSS

Summary

CVE-2024-26242 is a high-severity Sensitive Data Storage in Improperly Locked Memory (CWE-591) vulnerability in Microsoft Windows 10 1507. Its CVSS base score is 7.0 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 27th 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 SC-39 (Process Isolation) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Windows Telephony Server Elevation of Privilege Vulnerability

CWE(s)
CWE-591CWE-362

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-35309Same product: Microsoft Windows 10 1507
CVE-2023-23407Same product: Microsoft Windows 10 1507
CVE-2023-35362Same product: Microsoft Windows 10 1507
CVE-2023-35360Same product: Microsoft Windows 10 1507
CVE-2023-38159Same product: Microsoft Windows 10 1507
CVE-2023-21535Same product: Microsoft Windows 10 1607
CVE-2023-21546Same product: Microsoft Windows 10 1607
CVE-2024-21446Same product: Microsoft Windows 10 1507
CVE-2024-21405Same product: Microsoft Windows 10 1507
CVE-2023-36403Same product: Microsoft Windows 10 1507

Affected Assets

microsoft
windows 10 1507
≤ 10.0.10240.20596 · ≤ 10.0.10240.20596
microsoft
windows 10 1607
≤ 10.0.14393.6897 · ≤ 10.0.14393.6897
microsoft
windows 10 1809
≤ 10.0.17763.5696
microsoft
windows 10 21h2
≤ 10.0.19044.4291
microsoft
windows 10 22h2
≤ 10.0.19045.4291
microsoft
windows 11 21h2
≤ 10.0.22000.2899
microsoft
windows 11 22h2
≤ 10.0.22621.3447
microsoft
windows 11 23h2
≤ 10.0.22631.3447
microsoft
windows server 2008
all versions, r2
microsoft
windows server 2012
all versions, r2
+4 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V10.4.2
  • V10.4.5
  • V15.1.3
  • V15.4.1

Mitigating Controls (NIST 800-53 r5) AI

SC-39 Process Isolation partial match

Maintaining separate execution domains for each process structurally eliminates unintended concurrent access to the same shared resources.

SC-4 Information in Shared System Resources partial match

Preventing unintended information transfer through shared system resources directly addresses the improper concurrent modification that defines a race condition.

Mitigating Controls (NIST CSF 2.0) AI

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

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper synchronization primitives and concurrency testing that prevent race conditions.

PR.DS-01 partial match
prevents

PR.DS-01 encryption of data-at-rest can protect swapped pages but does not stop improper memory locking, addressing only one exposure facet of the weakness.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can discover unlocked sensitive buffers, but does not itself implement the locking mechanism.

A.8.24 Use of cryptography partial match
degrades

Cryptographic controls can reduce exposure of sensitive data even if it is paged, but do not directly enforce memory locking.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates concurrency controls and synchronization primitives that directly prevent race conditions.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify thread-safety and locking rules, but do not prescribe implementation details.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require proper synchronization and resource isolation, addressing the root cause of CWE-362.

A.8.28 Secure coding partial match
prevents

Secure-coding standards can mandate use of locked-memory APIs, directly preventing the weakness.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248525 All OL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at-rest protection. prevents CWE-591

References