CVE-2024-38173: Microsoft Outlook Remote Code Execution Vulnerability
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.66% (FIRST EPSS); higher than 52.2% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: Microsoft 365 Apps for Enterprise for 32-bit Systems https://aka.ms/OfficeSecurityReleases; Microsoft 365 Apps for Enterprise for 64-bit Systems https://aka.ms/OfficeSecurityReleases; Microsoft Office 2019 for 32-bit editions https://aka.ms/OfficeSecurityReleases.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Microsoft 365 Apps for Enterprise for 32-bit Systems https://aka.ms/OfficeSecurityReleases; Microsoft 365 Apps for Enterprise for 64-bit Systems https://aka.ms/OfficeSecurityReleases; Microsoft Office 2019 for 32-bit editions https://aka.ms/OfficeSecurityReleases or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Aug 13, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- CWE-73
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 6.7
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | 365 apps | cpe:2.3:a:microsoft:365_apps |
| microsoft | office | cpe:2.3:a:microsoft:office |
| microsoft | office long term servicing channel | cpe:2.3:a:microsoft:office_long_term_servicing_channel |
| microsoft | outlook | cpe:2.3:a:microsoft:outlook |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Microsoft 365 Apps for Enterprise
- 16.0.1 and later · before https://aka.ms/OfficeSecurityReleasesaffected
Microsoft Microsoft Office 2019
- 19.0.0 and later · before https://aka.ms/OfficeSecurityReleasesaffected
Microsoft Microsoft Office LTSC 2021
- 16.0.1 and later · before https://aka.ms/OfficeSecurityReleasesaffected
Microsoft Microsoft Outlook 2016
- 16.0.0.0 and later · before 16.0.5461.1001affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft 365 appsall versions
- microsoft office2019
- microsoft office long term servicing channel2021
- microsoft outlook2016
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-23397Microsoft Outlook Elevation of Privilege VulnerabilityKEV98Now
- CVE-2024-21413Microsoft Outlook Remote Code Execution VulnerabilityKEV97Now
- CVE-2026-21509Microsoft Office Security Feature Bypass VulnerabilityKEV82Now
Published before and after this one in the same product
- ← EarlierCVE-2024-38171Aug 13, 2024 · Microsoft PowerPoint Remote Code Execution Vulnerability31Monitor
- ← EarlierCVE-2024-38172Aug 13, 2024 · Microsoft Excel Remote Code Execution Vulnerability31Monitor
- Later →CVE-2024-38189Aug 13, 2024 · Microsoft Project Remote Code Execution VulnerabilityKEV67This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Microsoft 365 Apps for Enterprise for 32-bit Systems | https://aka.ms/OfficeSecurityReleases · Click to Run | Microsoft (MSRC) |
| Microsoft 365 Apps for Enterprise for 64-bit Systems | https://aka.ms/OfficeSecurityReleases · Click to Run | Microsoft (MSRC) |
| Microsoft Office 2019 for 32-bit editions | https://aka.ms/OfficeSecurityReleases · Click to Run | Microsoft (MSRC) |
| Microsoft Office 2019 for 64-bit editions | https://aka.ms/OfficeSecurityReleases · Click to Run | Microsoft (MSRC) |
| Microsoft Office LTSC 2021 for 32-bit editions | https://aka.ms/OfficeSecurityReleases · Click to Run | Microsoft (MSRC) |
| Microsoft Office LTSC 2021 for 64-bit editions | https://aka.ms/OfficeSecurityReleases · Click to Run | Microsoft (MSRC) |
| Microsoft Outlook 2016 (32-bit edition) | 16.0.5461.1001 · KB5002626 | Microsoft (MSRC) |
| Microsoft Outlook 2016 (64-bit edition) | 16.0.5461.1001 · KB5002626 | Microsoft (MSRC) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1236 · Aug 14, 2024(Microsoft Outlook Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-73 · External Control of File Name or PathCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Leverage Alternate EncodingCAPEC-267likelihood: High · High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- URL EncodingCAPEC-72likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
- Using UTF-8 Encoding to Bypass Validation LogicCAPEC-80likelihood: High · High
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.