CVE-2025-27477

8.8 HIGH

📋 TL;DR

A heap-based buffer overflow vulnerability in Windows Telephony Service allows remote attackers to execute arbitrary code without authentication. This affects Windows systems with the Telephony Service enabled, potentially allowing complete system compromise. Network-accessible systems are particularly vulnerable.

💻 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: ⚠️ Yes
Notes: Systems with Telephony Service disabled or blocked by firewall are less vulnerable. Server Core installations may be unaffected if Telephony Service is not installed.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise with administrative privileges, enabling data theft, ransomware deployment, or persistent backdoor installation across the network.

🟠

Likely Case

Remote code execution leading to malware installation, credential harvesting, and lateral movement within the network environment.

🟢

If Mitigated

Limited impact with proper network segmentation and endpoint protection, potentially reduced to denial of service or failed exploitation attempts.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires network access to the Telephony Service port (typically TCP 1720 or 1723). The vulnerability is in a core Windows service, making reliable exploitation challenging but possible.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Microsoft Security Update Guide for specific KB numbers

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

Restart Required: Yes

Instructions:

1. Apply the latest Windows security updates from Microsoft Update. 2. Restart the system to complete installation. 3. Verify the patch is applied using Windows Update history.

🔧 Temporary Workarounds

Disable Windows Telephony Service

windows

Stops the vulnerable service from running

sc stop TapiSrv
sc config TapiSrv start= disabled

Block Telephony Service Ports

windows

Prevents network access to the vulnerable service

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

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate systems running Telephony Service
  • Deploy endpoint detection and response (EDR) solutions to detect exploitation attempts

🔍 How to Verify

Check if Vulnerable:

Check if Telephony Service is running: sc query TapiSrv

Check Version:

systeminfo | findstr /B /C:"OS Name" /C:"OS Version"

Verify Fix Applied:

Verify Windows Update history contains the relevant security update KB number

📡 Detection & Monitoring

Log Indicators:

  • Unusual process creation from TapiSrv.exe
  • Crash logs related to telephony service
  • Windows Event ID 1000 application crashes

Network Indicators:

  • Unusual traffic to TCP ports 1720/1723 from unexpected sources
  • Multiple connection attempts to Telephony Service

SIEM Query:

source="windows" AND (process_name="TapiSrv.exe" AND (event_id=1000 OR parent_process="*"))

🔗 References

📤 Share & Export