Important CVSS 8.8 EPSS 0.01673 🔬 Patch diffed 2025-03 archive

Executive Summary

Heap-based buffer overflow in Windows Telephony Server allows an unauthorized attacker to execute code over a network.

Overview

8.8
CVSS HIGH
Important
MS Severity
Not Exploited
MS Exploit Status
Less Likely
MS Exploit Likelihood
Category Remote Code Execution
Released Mar 11 2025
Last Updated Mar 11 2025
Publicly Disclosed No
CISA KEV Not Listed
Known Exploits None Known
EPSS Score 0.01673 — 0.74751 percentile
NVD CVSS 8.8 HIGH — matches MSRC

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
ATTACK VECTOR
Network
ATTACK COMPLEXITY
Low
PRIVILEGES REQUIRED
None
USER INTERACTION
Required
SCOPE
Unchanged
CONFIDENTIALITY
High
INTEGRITY
High
AVAILABILITY
High
EXPLOIT CODE MATURITY
Unproven
REMEDIATION LEVEL
Official Fix
REPORT CONFIDENCE
Confirmed
Temporal Score: 7.7

EPSS Score

0.01673
probability of exploitation in the next 30 days
0.74751 percentile - updated 2026-08-14
View on FIRST.org

Affected Products

25 affected products
Product KB Article Severity Impact Restart Required
Windows 10 for 32-bit Systems 5053618 (Security Update) Important Remote Code Execution Yes
Windows 10 for x64-based Systems 5053618 (Security Update) Important Remote Code Execution Yes
Windows 10 Version 1607 for 32-bit Systems 5053594 (Security Update) Important Remote Code Execution Yes
Windows 10 Version 1607 for x64-based Systems 5053594 (Security Update) Important Remote Code Execution Yes
Windows 10 Version 1809 for 32-bit Systems 5053596 (Security Update) Important Remote Code Execution Yes
Windows 10 Version 1809 for x64-based Systems 5053596 (Security Update) Important Remote Code Execution Yes
Windows 10 Version 21H2 for 32-bit Systems 5053606 (Security Update) Important Remote Code Execution Yes
Windows 10 Version 21H2 for ARM64-based Systems 5053606 (Security Update) Important Remote Code Execution Yes
Windows 10 Version 21H2 for x64-based Systems 5053606 (Security Update) Important Remote Code Execution Yes
Windows 10 Version 22H2 for 32-bit Systems 5053606 (Security Update) Important Remote Code Execution Yes
Windows 10 Version 22H2 for ARM64-based Systems 5053606 (Security Update) Important Remote Code Execution Yes
Windows 10 Version 22H2 for x64-based Systems 5053606 (Security Update) Important Remote Code Execution Yes
Windows 11 Version 22H2 for ARM64-based Systems 5053602 (Security Update) Important Remote Code Execution Yes
Windows 11 Version 22H2 for x64-based Systems 5053602 (Security Update) Important Remote Code Execution Yes
Windows 11 Version 23H2 for ARM64-based Systems 5053602 (Security Update) Important Remote Code Execution Yes
Windows 11 Version 23H2 for x64-based Systems 5053602 (Security Update) Important Remote Code Execution Yes
Windows 11 Version 24H2 for ARM64-based Systems 5053598 (Security Update) 5053636 (SecurityHotpatchUpdate) Important Remote Code Execution 5051987 5052105 Base: 8.8 Temporal: 7.7 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.26100.3476 10.0.26100.3403 Yes None Windows 11 Version 24H2 for x64-based Systems 5053598 (Security Update) 5053636 (SecurityHotpatchUpdate) Important Remote Code Execution 5051987 5052105 Base: 8.8 Temporal: 7.7 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.26100.3476 10.0.26100.3403 Yes None Windows Server 2008 for 32-bit Systems Service Pack 2 5053888 (Monthly Rollup) 5053995 (Security Only) Important Remote Code Execution 5052038 Base: 8.8 Temporal: 7.7 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.23168 Yes None Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) 5053888 (Monthly Rollup) 5053995 (Security Only) Important Remote Code Execution 5052038 Base: 8.8 Temporal: 7.7 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.23168 Yes None Windows Server 2008 for x64-based Systems Service Pack 2 5053888 (Monthly Rollup) 5053995 (Security Only) Important Remote Code Execution 5052038 Base: 8.8 Temporal: 7.7 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.23168 Yes None Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) 5053888 (Monthly Rollup) 5053995 (Security Only) Important Remote Code Execution 5052038 Base: 8.8 Temporal: 7.7 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.23168 Yes None Windows Server 2008 R2 for x64-based Systems Service Pack 1 5053620 (Monthly Rollup) 5053627 (Security Only) Important Remote Code Execution 5052016 Base: 8.8 Temporal: 7.7 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.1.7601.27618 Yes None Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) 5053620 (Monthly Rollup) 5053627 (Security Only) Important Remote Code Execution 5052016 Base: 8.8 Temporal: 7.7 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.1.7601.27618 Yes None Windows Server 2012 5053886 (Monthly Rollup) Important Remote Code Execution Yes
Windows Server 2012 (Server Core installation) 5053886 (Monthly Rollup) Important Remote Code Execution Yes
Windows Server 2012 R2 5053887 (Monthly Rollup) Important Remote Code Execution Yes
Windows Server 2012 R2 (Server Core installation) 5053887 (Monthly Rollup) Important Remote Code Execution Yes
Windows Server 2016 5053594 (Security Update) Important Remote Code Execution Yes
Windows Server 2016 (Server Core installation) 5053594 (Security Update) Important Remote Code Execution Yes
Windows Server 2019 5053596 (Security Update) Important Remote Code Execution Yes
Windows Server 2019 (Server Core installation) 5053596 (Security Update) Important Remote Code Execution Yes
Windows Server 2022 5053603 (Security Update) 5053638 (SecurityHotpatchUpdate) Important Remote Code Execution 5051979 5052106 Base: 8.8 Temporal: 7.7 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.20348.3328 10.0.20348.3270 Yes None Windows Server 2022 (Server Core installation) 5053603 (Security Update) 5053638 (SecurityHotpatchUpdate) Important Remote Code Execution 5051979 5052106 Base: 8.8 Temporal: 7.7 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.20348.3328 10.0.20348.3270 Yes None Windows Server 2022, 23H2 Edition (Server Core installation) 5053599 (Security Update) Important Remote Code Execution Yes

Patches

8 patches
Article Type Restart
5053618 Security Update Yes
5053594 Security Update Yes
5053596 Security Update Yes
5053606 Security Update Yes
5053602 Security Update Yes
5053886 Monthly Rollup Yes
5053887 Monthly Rollup Yes
5053599 Security Update Yes

Patch Diff

ghidriff · tapisrv.dll (KB5053598)

Integer overflow leading to a heap-based buffer overflow (CWE-122) in the Windows Telephony Service tapisrv.dll priority-list readers, remote code execution on a client that connects to a malicious telephony server (Important, RCE, AV:N, UI:R, CVSS 8.8). GetPriorityList / GetMediaModesPriorityLists / LSetAppPriority build media-mode/app priority lists by allocating HeapAlloc(ghTapisrvHeap, value_size + 2) and filling it with value_size bytes (RegQueryValueExW), reserving 2 bytes for a wide terminator. PRE (.3037): the value_size <= value_size + 2 overflow check was gated behind Feature_1390216506 and BYPASSED when the flag was disabled, so a size near 0xFFFFFFFF made value_size + 2 wrap to a tiny allocation that was then overrun by the full-size copy - a heap overflow. Because the Telephony Service processes data from the telephony server the client connects to, MSRC classifies this as RCE on the client connecting to a malicious server. Diff of tapisrv.dll 10.0.26100.3037 -> .3323 (Mar 11 2025, KB5053598; vsize 380928 -> 372736, 25 funcs removed) confirms the fix: the fixed build enforces the value_size <= value_size + 2 overflow guard UNCONDITIONALLY (removing the Feature_1390216506 bypass) before the allocation and copy, and bounds the terminator write; LSetAppPriority also gains bounded 0x104/MAX_PATH app-name handling. Stated at confirmed-changed level (broad priority-list rework; the isolable mechanism is the always-enforced allocation overflow guard).

Pre-patch version 10.0.26100.3037 Download
Post-patch version 10.0.26100.3323 Download
Function Address Change Note
GetPriorityList / GetMediaModesPriorityLists code change code (priority-list allocation overflow guard made unconditional) Pre (.3037): HeapAlloc(value_size + 2) guarded by (Feature_1390216506 disabled || value_size <= value_size + 2) - the overflow check was skipped when the flag was off, so a near-UINT_MAX value_size wrapped to a tiny allocation and was overrun. Post (.3323): value_size <= value_size + 2 enforced unconditionally before HeapAlloc and the RegQueryValueExW copy; terminator write bounded.
LSetAppPriority code change code (bounded app-name length handling) Reworked with a 0x104/MAX_PATH-bounded length loop for the application-name string used to set priority.
Feature_1390216506 gate gate (bypass removed) Pre-patch this CFR flag gated the priority-list overflow check (bypassable when disabled); the fixed build enforces the check unconditionally.
View full diff report View RCA report

Root Cause Analysis

CVE-2025-24056 — Windows Telephony Service tapisrv.dll Priority-List Allocation Integer Overflow → Heap Buffer Overflow (RCE)


Summary

Product Windows — tapisrv.dll (Windows Telephony Service / TAPI Server)
CVE ID CVE-2025-24056
Impact Remote Code Execution (on a client that connects to a malicious telephony server)
MSRC severity Important
CVSS 8.8 / 7.7 — CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CWE CWE-122: Heap-based Buffer Overflow (via integer overflow)
Delivery Network — client is tricked into connecting to a malicious telephony server (UI:R)
KB / Fixed build KB5053598 — tapisrv.dll 10.0.26100.3323 (Win11 24H2 x64)
Patch Date March 11, 2025 (2025-Mar)
Pre-patch binary tapisrv.dll 10.0.26100.3037 — SHA256 7cde3632cc64c832593ce03e3d5f61eb22fb12253af2a35d618e36efcdb378db
Post-patch binary tapisrv.dll 10.0.26100.3323 — SHA256 c0fbaec69f5495be56c3d4de2a56aa55a538171600024d8be084a8a7e6fa6ce2
Feature flag Feature_1390216506 — gated the check pre-patch; the fixed build makes it unconditional
Exploitability Exploitation Less Likely; not publicly disclosed; not exploited (per MSRC)

Product Description

tapisrv.dll implements the Windows Telephony Service (TAPI Server). It builds media-mode / application priority lists from configuration values via GetPriorityList, GetMediaModesPriorityLists, and LSetAppPriority. Each reads a priority-list value into a heap buffer allocated from the TAPI heap (HeapAlloc(ghTapisrvHeap, …)), prefixing a quote character and reserving two extra bytes for a wide-char terminator.


Vulnerability Summary

The priority-list readers size the destination buffer as value_size + 2 and pass that to HeapAlloc, then fill it with value_size bytes (RegQueryValueExW). When the check on the size was bypassable (see below), a value_size near 0xFFFFFFFF would make value_size + 2 wrap to a tiny value (CWE-190), producing an undersized heap allocation that is then overrun by the full-size read — a heap-based buffer overflow (CWE-122). Because the Telephony Service processes data on behalf of a telephony server the client connects to, MSRC classifies this as remote code execution on the client that connects to a malicious server (AV:N, UI:R).

Confirmation level: the diff is a broad tapisrv.dll priority-list rework (4 code-changed functions, 20 modified, 25 removed) under the flag Feature_1390216506. The isolable security mechanism is the value_size <= value_size + 2 integer- overflow guard on the priority-list allocation, which the fixed build enforces unconditionally; stated here at confirmed-changed level.


Prerequisites and Constraints

  • Network with user interaction (AV:N, PR:N, UI:R): the victim’s client is induced to connect to a malicious telephony server that supplies the oversized priority-list data.
  • The size driving HeapAlloc(value_size + 2) is near UINT_MAX so the + 2 wraps.
  • Result: an undersized TAPI-heap buffer is allocated and then overrun.

Vulnerability Details

Root Cause

The priority-list allocation size value_size + 2 was computed without an always-enforced overflow check, so a near-UINT_MAX size wrapped to a small allocation that was subsequently overrun by a full-size copy.

The patch (confirmed — diff, .3037 → .3323)

Pre-patch, the overflow check in the priority-list readers was gated behind Feature_1390216506 and bypassable when the flag was disabled:

// GetMediaModesPriorityLists (10.0.26100.3037) — PRE (from the diff)
if ( ... && (Feature_1390216506__private_IsEnabled() == 0
             || (value_size <= value_size + 2)) ) {           // check skipped when flag OFF
    _Str = HeapAlloc(ghTapisrvHeap, 8, (ulonglong)(value_size + 2));
    ...
}

The fixed build enforces the value_size <= value_size + 2 guard unconditionally (no feature bypass) before the allocation and copy:

// GetPriorityList / GetMediaModesPriorityLists (10.0.26100.3323) — PATCHED (from the diff)
if ((LVar1 == 0) && (value_size != 0)) {
    if (value_size <= value_size + 2) {                        // *** overflow guard, always enforced ***
        _Str = HeapAlloc(ghTapisrvHeap, 8, (ulonglong)(value_size + 2));
        if (_Str != NULL) {
            *_Str = L'\"';
            LVar1 = RegQueryValueExW(param_1, param_2, NULL, local_res20, (LPBYTE)(_Str + 1), &value_size);
            if ((LVar1 == 0) && (1 < value_size)) {
                *(WCHAR*)((longlong)_Str + ((value_size - 2) & ~1) + 2) = 0;   // bounded terminator
                ...
            } else ServerFree(_Str);
        }
    }
}

With the overflow guard always enforced, a wrapped value_size + 2 no longer yields an undersized allocation, so the priority-list buffer can no longer be overrun, closing the integer-overflow-to-heap-overflow. (LSetAppPriority similarly gains a bounded 0x104/MAX_PATH length handling for the app-name string.)

Patch Completeness Assessment

The guard is enforced unconditionally in the fixed build (Feature_1390216506 previously allowed the check to be skipped). Apply KB5053598 or later; the flag no longer needs to be enabled for the fix to be active on the patched binary.


Detection Guidance

Behavioural. Heap corruption / crashes in tapisrv!GetPriorityList / GetMediaModesPriorityLists / LSetAppPriority within the Telephony Service on unpatched builds; clients connecting to untrusted telephony servers. Restrict TAPI usage and outbound telephony connections to trusted endpoints.

Config. In the fixed build the guard is unconditional; on the pre-patch build it depended on Feature_1390216506.


References

  • MSRC advisory — CVE-2025-24056 (Windows Telephony Service Remote Code Execution), released 2025-03-11, KB5053598.
  • Full binary diff: /data/patch_diffs/tapisrv_dll-cve-2025-24056-ghidriff.md

Attack Path

A malicious telephony server supplies an oversized priority-list value; the size+2 allocation overflows and the buffer is overrun

Attack path for CVE-2025-24056 A malicious telephony server supplies an oversized priority-list value; the size+2 allocation overflows and the buffer is overrun 01 — ENTRY Client is tricked into connecting to a malicious telephony server The Windows Telephony Service (tapisrv.dll) processes priority-list data on the client. AV:N / PR:N / UI:R (network, requires the user to connect). 02 — CONTROLLED INPUT Server supplies a priority-list value size near UINT_MAX value_size drives HeapAlloc(ghTapisrvHeap, value_size + 2) in GetPriorityList / GetMediaModesPriorityLists. 03 — MISSING CHECK value_size + 2 wraps -> undersized allocation (CWE-190 -> CWE-122) With the overflow check bypassed (Feature_1390216506 off), the +2 addition wraps to a tiny size, so a short buffer is allocated for a full-size copy. 04 — IMPACT Undersized TAPI-heap buffer overrun -> code execution The full-size RegQueryValueExW copy overruns the short buffer - a heap overflow in the Telephony Service, exploitable for remote code execution on the client.

Derived from the patch delta: the checks added by the vendor identify which fields crossed a trust boundary unvalidated. Reachability and privilege are taken from the call chain in the RCA report.

Exploits & PoC

Detection Rules

Acknowledgments

Anonymous