Cyber Resilience

CVE-2025-53810

Memory Safety in Microsoft Windows Server 2008 r2

Memory Safety
Published
09 September 2025
Modified
02 October 2025
Patch / advisory
View advisory
CVSS Score v3.1 6.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0047 38th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2025-53810 is a medium-severity Type Confusion (CWE-843) vulnerability in Microsoft Windows Server 2008. Its CVSS base score is 6.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 38th percentile by exploit likelihood (below the median); 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 SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Access of resource using incompatible type ('type confusion') in Windows Defender Firewall Service allows an authorized attacker to elevate privileges locally.

CWE(s)
CWE-843

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
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 →
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 →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-54104Same product: Microsoft Windows 10 1507
CVE-2025-54915Same product: Microsoft Windows 10 1507
CVE-2025-53143Same product: Microsoft Windows 10 1507
CVE-2025-54109Same product: Microsoft Windows 10 1507
CVE-2025-48815Same product: Microsoft Windows 10 1507
CVE-2025-54094Same product: Microsoft Windows 10 1507
CVE-2025-53808Same product: Microsoft Windows 10 1507
CVE-2025-30397Same product: Microsoft Windows 10 1507
CVE-2025-53144Same product: Microsoft Windows 10 1507
CVE-2025-53145Same product: Microsoft Windows 10 1507

Affected Assets

microsoft
windows 10 1507
≤ 10.0.10240.21128 · ≤ 10.0.10240.21128
microsoft
windows 10 1607
≤ 10.0.14393.8422 · ≤ 10.0.14393.8422
microsoft
windows 10 1809
≤ 10.0.17763.7792 · ≤ 10.0.17763.7792
microsoft
windows 10 21h2
≤ 10.0.19044.6332
microsoft
windows 10 22h2
≤ 10.0.19045.6332
microsoft
windows 11 22h2
≤ 10.0.22621.5909
microsoft
windows 11 23h2
≤ 10.0.22631.5909
microsoft
windows 11 24h2
≤ 10.0.26100.6508
microsoft
windows server 2008
all versions, r2
microsoft
windows server 2012
all versions, r2
+5 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V3.2.3
  • V15.3.5

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and type-aware analysis) directly finds type-confusion flaws before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require use of type-safe languages, static typing, and runtime type checks that structurally avoid allocating one type and accessing another.

SI-16 Memory Protection partial match

Memory-protection controls limit the blast radius when a type-confusion access occurs but do not stop the flaw itself.

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 prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.

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

Security testing in development can detect type-confusion vulnerabilities through fuzzing and static analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify strong typing and interface contracts that reduce type confusion.

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

Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.

References