Security Resilience

CVE-2024-21387

Microsoft Edge Chromium ≤ 120.0.2210.160

Published
26 January 2024
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0072 53th percentile
Risk Priority 50 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-21387 is a medium-severity Insufficient UI Warning of Dangerous Operations (CWE-357) vulnerability in Microsoft Edge Chromium. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Microsoft Edge for Android Spoofing Vulnerability

CWE(s)
CWE-357NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
attack.mitre.org →
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
attack.mitre.org →
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
attack.mitre.org →
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
attack.mitre.org →
T1003.007 Proc Filesystem Credential Access
Adversaries may gather credentials from the proc filesystem or `/proc`.
attack.mitre.org →
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-49054Same product: Microsoft Edge Chromium
CVE-2026-58597Same product: Microsoft Edge Chromium
CVE-2024-43580Same product: Microsoft Edge Chromium
CVE-2024-21336Same product: Microsoft Edge Chromium
CVE-2024-30058Same product: Microsoft Edge Chromium
CVE-2024-38207Same product: Microsoft Edge Chromium
CVE-2024-38218Same product: Microsoft Edge Chromium
CVE-2023-24892Same product: Microsoft Edge Chromium
CVE-2023-24935Same product: Microsoft Edge Chromium
CVE-2024-38210Same product: Microsoft Edge Chromium

Affected Assets

microsoft
edge chromium
≤ 120.0.2210.160 · ≤ 121.0.2277.83

Mitigating Controls

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.

PR.PS-06 partial match
blocks

Secure SDLC practices directly encompass designing noticeable UI warnings for risky operations.

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.

A.6.7 Remote working partial match
removes
A.8.19 Installation of software on operational systems partial match
removes
A.8.25 Secure development life cycle partial match
blocks

Secure development lifecycle requires usable security prompts and warnings to be designed into the UI.

A.8.26 Application security requirements partial match
blocks

A.8.26 only requires that security requirements (including UI-related ones) be identified and specified during development; it does not itself enforce, implement, or make any UI warning noticeable enough to stop exploitation of CWE-357

A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates establishing and applying security engineering principles (e.g. least privilege, security by design, fail securely) and design reviews during the SDLC; this does not stop a UI from presenting an insufficiently noticeable warning for dangerous operations, which can still be exploited.

A.8.28 Secure coding partial match
prevents

Secure coding practices include implementing noticeable, effective UI warnings for risky actions.

References