CVE-2025-21240

8.8 HIGH

📋 TL;DR

This vulnerability in Windows Telephony Service allows remote attackers to execute arbitrary code with SYSTEM privileges by sending specially crafted packets to a vulnerable system. It affects Windows systems with the Telephony service enabled, primarily impacting enterprise environments using telephony integration features.

💻 Affected Systems

Products:
  • Windows Telephony Service
Versions: Windows 10, Windows 11, Windows Server 2016, Windows Server 2019, Windows Server 2022
Operating Systems: Windows
Default Config Vulnerable: ✅ No
Notes: Only vulnerable when Telephony service is enabled and running. Many systems have this disabled by default unless specifically configured for telephony integration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise with SYSTEM privileges, enabling lateral movement, data exfiltration, ransomware deployment, and persistent backdoor installation across the network.

🟠

Likely Case

Initial foothold for attackers leading to privilege escalation, credential harvesting, and deployment of additional malware payloads within the target environment.

🟢

If Mitigated

Limited impact due to network segmentation, restricted service exposure, and proper access controls preventing successful exploitation attempts.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires network access to the Telephony service port (typically TCP 1720). No authentication is required if service is exposed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: May 2025 Security Update or later

Vendor Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21240

Restart Required: Yes

Instructions:

1. Apply May 2025 Windows Security Update via Windows Update. 2. Alternatively, download and install the standalone security update from Microsoft Update Catalog. 3. Restart the system to complete installation.

🔧 Temporary Workarounds

Disable Telephony Service

Windows

Disable the Telephony service if not required for business operations

sc config TapiSrv start= disabled
sc stop TapiSrv

Block Telephony Service Port

Windows

Block network access to Telephony service port (TCP 1720) at firewall

netsh advfirewall firewall add rule name="Block Telephony" dir=in action=block protocol=TCP localport=1720

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate systems with Telephony service
  • Deploy host-based intrusion prevention rules to detect and block exploitation attempts

🔍 How to Verify

Check if Vulnerable:

Check if Telephony service is running: sc query TapiSrv | findstr "RUNNING"

Check Version:

systeminfo | findstr "OS Name"

Verify Fix Applied:

Verify patch installation: wmic qfe list | findstr "KB5037768" (replace with actual KB number)

📡 Detection & Monitoring

Log Indicators:

  • Event ID 4688 with Telephony service parent process
  • Unusual network connections to port 1720
  • Failed Telephony service authentication attempts

Network Indicators:

  • Unusual traffic patterns to TCP port 1720
  • Malformed packets targeting Telephony service

SIEM Query:

source="windows" AND (event_id=4688 AND process_name="svchost.exe" AND service_name="TapiSrv") OR (destination_port=1720 AND protocol="TCP")

🔗 References

📤 Share & Export