Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS 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
- 🇪🇺 ENISA EUVD: EUVD-2023-39314
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
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.4.2V17.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.
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.
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.
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.
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.
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.