Cyber Resilience

CVE-2023-35378

Race Condition in Microsoft Windows 10 1809 ≤ 10.0.17763.4737

Race Condition
Published
08 August 2023
Modified
10 August 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 28th percentile
Risk Priority 51 floored blend · peak EPSS

Summary

CVE-2023-35378 is a high-severity Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 7.0 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Windows Projected File System Elevation of Privilege Vulnerability

CWE(s)
CWE-367CWE-362

Related Threats

MITRE ATT&CK Enterprise Techniques

T1034 Path Interception Persistence
**This technique has been deprecated.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
T1574 Hijack Execution Flow Stealth
Adversaries may execute their own malicious payloads by hijacking the way operating systems run programs.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-24861Same product: Microsoft Windows 10 1809
CVE-2024-26218Same product: Microsoft Windows 10 1809
CVE-2024-35265Same product: Microsoft Windows 10 1809
CVE-2023-36698Same product: Microsoft Windows 10 1809
CVE-2024-38186Same product: Microsoft Windows 10 1809
CVE-2024-21362Same product: Microsoft Windows 10 1809
CVE-2023-38141Same product: Microsoft Windows 10 1809
CVE-2024-30099Same product: Microsoft Windows 10 1809
CVE-2024-30088Same product: Microsoft Windows 10 1809
CVE-2023-33154Same product: Microsoft Windows 10 1809

Affected Assets

microsoft
windows 10 1809
≤ 10.0.17763.4737
microsoft
windows 10 21h2
≤ 10.0.19044.3324
microsoft
windows 10 22h2
≤ 10.0.19045.3324
microsoft
windows 11 21h2
≤ 10.0.22000.2295
microsoft
windows 11 22h2
≤ 10.0.22621.2134
microsoft
windows server 2019
all versions
microsoft
windows server 2022
all versions

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V10.4.2
  • V10.4.5
  • V15.1.3
  • V15.4.1

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

AU-8 Time Stamps
addresses: CWE-362 CWE-367

Accurate timestamps from internal clocks enable detection of race conditions by providing reliable event ordering in audit logs.

PL-6 Security-related Activity Planning
addresses: CWE-362

Coordination of concurrent security activities reduces the probability that shared resources will be accessed simultaneously without proper synchronization.

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 include coding standards and reviews that prevent TOCTOU race conditions.

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 detect race conditions, but does not prevent them at design or coding time.

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 explicitly forbid unsafe concurrent access patterns and mandate atomic operations or locks.

A.8.17 Clock synchronization none match
none

Reliable, synchronized time across systems narrows the exploitable window in which a resource state can change between a security check and its use.

References