Cyber Resilience

CVE-2023-35310

Race Condition in Microsoft Windows Server 2008 r2

Race Condition
Published
11 July 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 6.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0066 48th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2023-35310 is a medium-severity Sensitive Data Storage in Improperly Locked Memory (CWE-591) vulnerability in Microsoft Windows Server 2008. Its CVSS base score is 6.6 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 48th 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 DNS Server Remote Code Execution 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-28278Same product: Microsoft Windows Server 2008
CVE-2023-35346Same product: Microsoft Windows Server 2008
CVE-2023-35344Same product: Microsoft Windows Server 2008
CVE-2023-33163Same product: Microsoft Windows Server 2008
CVE-2023-28255Same product: Microsoft Windows Server 2008
CVE-2023-35345Same product: Microsoft Windows Server 2008
CVE-2023-28256Same product: Microsoft Windows Server 2008
CVE-2025-30394Same product: Microsoft Windows Server 2012
CVE-2023-21766Same product: Microsoft Windows Server 2016
CVE-2024-38263Same product: Microsoft Windows Server 2008

Affected Assets

microsoft
windows server 2008
all versions, r2
microsoft
windows server 2012
all versions, r2
microsoft
windows server 2016
all versions
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)
  • 1 hardening rule · 1 OS baseline
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

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 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