cve.bz

CVE-2023-35311 Microsoft Outlook Security Feature Bypass Vulnerability

8.8 highKEVEPSS 16%Fix available

High (8.8) in Microsoft Outlook. In CISA KEV since 2023-07-11. EPSS 16% estimated probability of exploitation activity in the next 30 days.

On this page
Microsoft Outlook Security Feature Bypass Vulnerability

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
16% (unchanged from 16% a week ago; 16% 30 days ago) estimated probability of exploitation activity in the next 30 days; 97th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2023-07-11, due 2023-08-01
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-02-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-35311 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-35311?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-35311?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-35311 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2023-35311

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2023-35311](https://cve.bz/cve/badge/CVE-2023-35311.svg)](https://cve.bz/cve/CVE-2023-35311)

HTML:

<a href="https://cve.bz/cve/CVE-2023-35311"><img src="https://cve.bz/cve/badge/CVE-2023-35311.svg" alt="CVE-2023-35311"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft 365 Apps for Enterprisefrom 16.0.1 before https://aka.ms/OfficeSecurityReleases
Microsoft Office LTSC 2021from 16.0.1 before https://aka.ms/OfficeSecurityReleases
Microsoft Office 2019from 19.0.0 before https://aka.ms/OfficeSecurityReleases
Microsoft Outlook 2016from 16.0.0.0 before 16.0.5404.1000
Microsoft Outlook 2013from 14.0.0 before 15.0.5571.1000
Microsoft Outlook 2013 Service Pack 1from 15.0.0.0 before 15.0.5571.1000

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON