CVE-2024-21413: Microsoft Outlook Improper Input Validation Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

Microsoft Outlook Remote Code Execution Vulnerability

Description quoted from the CVE record (assigned by microsoft, published 2024-02-13).

Weakness: CWE-20: Improper Input Validation

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: total.

On CISA KEV since
2025-02-06
US federal deadline
2025-02-27
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2024-01322, CNNVD-202402-1028, CNVD-2024-34110, EUVD-2024-19122, GHSA-9mp4-h7q5-2rgq

VEDAS cluster: VEDAS:BERKELIUMBREAK

Exploit Observer links 48 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (48)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (1)

Vulnerability databases and vendor advisories (15)

Catalogue entries, not exploit evidence.

1372 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.947
very likely to be attacked soon
VEDAS
0.976
strong exploit evidence
On CISA KEV
Yes, since 2025-02-06
Detection rule
None yet
EPSS (chance of attack)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.1CVE-2024-21413 EPSS over time2025-042026-11-01
VEDAS (exploit evidence)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.9CVE-2024-21413 VEDAS over time2025-042026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
Microsoft Microsoft 365 Apps for Enterprisefrom 16.0.1 before https://aka.ms/OfficeSecurityReleasesNot stated
Microsoft Microsoft Office 2016from 16.0.0 before 16.0.5435.1001Not stated
Microsoft Microsoft Office 2019from 19.0.0 before https://aka.ms/OfficeSecurityReleasesNot stated
Microsoft Microsoft Office LTSC 2021from 16.0.1 before https://aka.ms/OfficeSecurityReleasesNot stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: microsoft 365_apps, microsoft office_2016, microsoft office_2019, microsoft office_long_term_servicing_channel, microsoft_corp microsoft_365_apps_for_enterprise, microsoft_corp microsoft_office_2016, microsoft_corp microsoft_office_2019, microsoft_corp microsoft_office_ltsc_2021.

How to fix it

Fixed versions stated in the CVE record: https://aka.ms/OfficeSecurityReleases, 16.0.5435.1001.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Vendor guidance:

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

References

Vendor advisories and patches

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.