Cyber Resilience

CVE-2024-49057

Microsoft Defender For Endpoint ≤ 1.0.7128.0101

Published
12 December 2024
Modified
08 January 2025
Patch / advisory
View advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
EPSS Score 0.017 75th percentile
Risk Priority 67 floored blend · peak EPSS

Summary

CVE-2024-49057 is a high-severity Improper Input Validation (CWE-20) vulnerability in Microsoft Defender For Endpoint. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 25% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Microsoft Defender for Endpoint on Android contains a spoofing vulnerability tracked as CVE-2024-49057. The flaw is rated 8.1 under CVSS 3.1 with an attack vector of network, low complexity, no required privileges, and required user interaction, resulting in high impact to confidentiality and integrity. It is associated with CWE-20 improper input validation.

An unauthenticated remote attacker can exploit the issue by sending crafted content that the application processes after user interaction. Successful exploitation allows spoofing actions that can expose or alter sensitive information handled by the endpoint protection agent without affecting availability.

The Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-49057 provides official mitigation guidance and patch information. Exploitation probability reached a peak of 0.0578 on 2025-12-18 after starting from a lower baseline before receding to the current value of 0.0297, indicating a temporary increase in observed interest following disclosure.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Microsoft Defender for Endpoint on Android Spoofing Vulnerability

CWE(s)
CWE-20NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1036.001 Invalid Code Signature Stealth
Adversaries may attempt to mimic features of valid code signatures to increase the chance of deceiving a user, analyst, or tool.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-21315Same product: Microsoft Defender For Endpoint
CVE-2025-62455Same vendor: Microsoft
CVE-2024-49073Same vendor: Microsoft
CVE-2023-21550Same vendor: Microsoft
CVE-2024-38021Same vendor: Microsoft
CVE-2025-59198Same vendor: Microsoft
CVE-2023-36406Same vendor: Microsoft
CVE-2025-47171Same vendor: Microsoft
CVE-2026-21229Same vendor: Microsoft
CVE-2023-21767Same vendor: Microsoft

Affected Assets

microsoft
defender for endpoint
≤ 1.0.7128.0101

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing input validation through analysis or test cases.

SI-10 Information Input Validation good match

SI-10 directly requires validity checks on information inputs, structurally preventing improper or missing validation.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can embed input-validation practices into the engineering process.

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 mostly match
prevents

Secure SDLC practices directly require and enforce input validation during development.

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.8.29 Security testing in development and acceptance mostly match
finds

Testing against a defined set of requirements and using code review plus vulnerability scanning forces validation of inputs and handling of unanticipated conditions, reducing the chance that malformed data will be accepted.

A.8.25 Secure development life cycle partial match
prevents

Secure-coding guidelines and mandatory security testing (including code scans) compel developers to validate and sanitize inputs at design and implementation time, lowering the incidence of malformed or malicious data reaching downstream components.

A.8.26 Application security requirements partial match
prevents

Mandating input controls that include integrity checks and input validation ensures that untrusted data is examined before use, blocking the root cause of many injection and malformed-data weaknesses.

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

Security-by-design principles explicitly call for data validation and sanitization at every layer, reducing the chance that malformed or malicious input will be processed without scrutiny.

A.8.28 Secure coding partial match
prevents

Requiring language-specific secure coding standards, peer review, SAST and documented mitigation of common programming errors forces validation of all inputs before they are trusted.

A.8.7 Protection against malware none match
none

Regular automated validation of system software and data content, combined with scanning of all inbound files, enforces input validation at the boundary before untrusted content is processed.

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).

RHEL 8 (1 rule)
  • V-230265 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-20

References