CVE-2024-21342

7.5 HIGH

📋 TL;DR

This vulnerability in Windows DNS Client allows an attacker to cause a denial of service (DoS) condition by sending specially crafted DNS responses. Affected systems include Windows 10, 11, Server 2016, 2019, and 2022. The vulnerability could cause system instability or crashes.

💻 Affected Systems

Products:
  • Windows DNS Client
Versions: Windows 10 versions 21H2 and 22H2, Windows 11 versions 21H2, 22H2, and 23H2, Windows Server 2016, 2019, and 2022
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Systems using Windows DNS Client are vulnerable by default when connected to networks where DNS responses can be manipulated.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system crash requiring reboot, potentially disrupting critical services on affected Windows systems.

🟠

Likely Case

Service disruption affecting DNS resolution and dependent applications, causing temporary unavailability.

🟢

If Mitigated

Minimal impact with proper network segmentation and monitoring; systems remain functional with potential performance degradation.

🌐 Internet-Facing: MEDIUM - Requires attacker to send malicious DNS responses, which could be achieved through DNS poisoning or man-in-the-middle attacks.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could exploit this to disrupt DNS services.

🎯 Exploit Status

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

Exploitation requires ability to send malicious DNS responses to target, which could be achieved through various network attacks.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: February 2024 security updates (KB5034765 for Windows 11, KB5034763 for Windows 10, etc.)

Vendor Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21342

Restart Required: Yes

Instructions:

1. Open Windows Update settings. 2. Check for updates. 3. Install February 2024 security updates. 4. Restart system when prompted.

🔧 Temporary Workarounds

Use alternative DNS resolver

windows

Configure systems to use third-party DNS software instead of Windows DNS Client

Network segmentation

all

Segment DNS traffic and restrict DNS response sources to trusted servers only

🧯 If You Can't Patch

  • Implement strict network controls to prevent untrusted DNS responses
  • Monitor for DNS-related crashes and implement redundancy for critical DNS services

🔍 How to Verify

Check if Vulnerable:

Check Windows version and installed updates; systems without February 2024 security updates are vulnerable.

Check Version:

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

Verify Fix Applied:

Verify February 2024 security updates are installed via Windows Update history or 'systeminfo' command.

📡 Detection & Monitoring

Log Indicators:

  • Event ID 1000 or 1001 in Application logs indicating DNS Client crashes
  • Increased DNS-related errors in system logs

Network Indicators:

  • Unusual DNS response patterns
  • DNS traffic from unexpected sources

SIEM Query:

EventID=1000 OR EventID=1001 AND SourceName="DNS Client"

🔗 References

📤 Share & Export