Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:HSummary
CVE-2023-33153 is a medium-severity Use After Free (CWE-416) vulnerability in Microsoft Office. Its CVSS base score is 6.8 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV 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.
CVE-2023-33153 is a remote code execution vulnerability affecting Microsoft Outlook, as indicated by its official description and assignment of CWE-416. The flaw carries a CVSS 3.1 base score of 6.8 with the vector AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H, reflecting network-accessible attack potential that requires user interaction and high attack complexity.
An unauthenticated remote attacker can leverage the issue to execute arbitrary code on a target system, resulting in high integrity and availability impacts while leaving confidentiality unaffected. Successful exploitation therefore allows an adversary to modify data or disrupt Outlook functionality after the victim interacts with malicious content delivered over the network.
Microsoft’s Security Response Center advisory at the referenced URL supplies official mitigation guidance, including available patches and recommended update actions for affected Outlook installations.
The associated EPSS score rose materially from a low baseline after the July 2023 disclosure, reaching a peak of 0.0673 on 2025-01-22 before receding to the current value of 0.0064; this trajectory indicates that exploitation interest emerged well after public release and warrants renewed attention.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-37338
Vulnerability Data
Microsoft Outlook Remote Code Execution Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 3 OS baselines
V1.4.3
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.
Use-after-free exploits that achieve arbitrary code execution are blocked or significantly hardened by non-executable pages and ASLR.
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.
Secure SDLC practices directly incorporate memory-safety tooling and reviews that prevent most use-after-free defects.
Vulnerability identification processes can discover use-after-free issues via scanning or analysis but do not prevent their introduction.
Routine patching removes known use-after-free instances after they have been introduced in released software.
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.
Security testing in development can detect use-after-free bugs before release.
Secure SDLC mandates memory-safety practices that reduce use-after-free defects.
Application security requirements can specify memory-management rules that mitigate use-after-free.
Secure architecture principles include memory-safety design choices that limit use-after-free exposure.
Secure coding standards directly prescribe avoidance of use-after-free patterns.
Change-management processes help ensure memory-safety fixes are deployed consistently.
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-248592 OL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416
RHEL 8 (1 rule)
- V-230279 RHEL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416
RHEL 9 (1 rule)
- V-257794 RHEL 9 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416