Security Resilience

CVE-2023-35311

Race Condition in Microsoft 365 Apps

CISA KEVActive ExploitationEUVD ExploitedRace Condition
Published
11 July 2023
Modified
08 October 2026
KEV Added
11 July 2023
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.16 97th percentile
Risk Priority 90 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-35311 is a high-severity Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367) vulnerability in Microsoft 365 Apps. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 3% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Microsoft Outlook contains a security feature bypass vulnerability tracked as CVE-2023-35311. The flaw, assigned CWE-367, resides in the client’s handling of messages or attachments and received a CVSS 3.1 score of 8.8 reflecting network attack vector, low complexity, no required privileges, and high impact on confidentiality, integrity, and availability.

An unauthenticated remote attacker can exploit the issue by sending a specially crafted message that triggers a race condition, allowing the security feature to be bypassed when the recipient interacts with the content. Successful exploitation can result in disclosure of sensitive information, modification of data, or full compromise of the Outlook process and underlying system.

Microsoft’s advisory directs customers to apply the security update released in July 2023; the vulnerability is also listed in CISA’s Known Exploited Vulnerabilities catalog, confirming that in-the-wild exploitation has been observed.

EPSS for the CVE rose sharply from a low baseline to a peak of 0.7572 on 28 October 2024 before receding, indicating that meaningful exploitation interest developed well after initial disclosure.

EU & UK References

Vulnerability Data

Microsoft Outlook Security Feature Bypass Vulnerability

CWE(s)
KEV Date Added
11 July 2023

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1553.001 Gatekeeper Bypass Defense Impairment
Adversaries may modify file attributes and subvert Gatekeeper functionality to evade user prompts and execute untrusted programs.
T1564.010 Process Argument Spoofing Stealth
Adversaries may attempt to hide process command-line arguments by overwriting process memory.
T1176 Software Extensions Persistence
Adversaries may abuse software extensions to establish persistent access to victim systems.
T1176.001 Browser Extensions Persistence
Adversaries may abuse internet browser extensions to establish persistent access to victim systems.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-30088Same vendor: Microsoftboth on KEV
CVE-2024-38186Same vendor: Microsoft
CVE-2023-21537Same vendor: Microsoft
CVE-2023-33156Same vendor: Microsoft
CVE-2026-20816Same vendor: Microsoft
CVE-2024-38153Same vendor: Microsoft
CVE-2023-38141Same vendor: Microsoft
CVE-2024-29062Same vendor: Microsoft
CVE-2024-43452Same vendor: Microsoft
CVE-2025-29969Same vendor: Microsoft

Affected Assets

microsoft
365 apps
all versions
microsoft
office 2019
all versions
microsoft
office 2021
all versions
microsoft
outlook
2013, 2016

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)
  • V15.4.2
  • V17.2.6

Likely Mitigating Controls

Our mappings. 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.

addresses: CWE-367

Timestamps meeting UTC or offset standards help identify TOCTOU issues through precise chronological reconstruction of check/use operations.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly include coding standards and reviews that prevent TOCTOU race conditions.

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

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

prevents

A.8.28 mandates secure coding practices (threat modelling, secure coding standards, peer review, test-driven development) that can prevent some TOCTOU instances by mandating atomic operations and file locking, but the clause governs a fallible human practice and TOCTOU is notoriously hard to catch in code review, leaving a nameable remainder of instances that slip through.

finds

A.8.29's programme covers manual code review (High for CWE-367), penetration testing/dynamic analysis (High), and automated static analysis (SOAR Partial), reaching the weakness through both SOURCE and RUNTIME; the remainder is the inherent difficulty of reliably triggering and observing race conditions during one cycle and the patterns automated tools miss.

finds

A.8.8's reach is DISCLOSURE — it sees only instances carrying a vendor-published flaw. TOCTOU does surface as CVEs (five observed examples in the CWE entry), so the weakness is not invisible to the clause, but the disclosed share is a minority: most CWE-367 instances live in first-party code that never receives a CVE, and A.8.8's scanning/inventory programme has no view of those.

References