CVE-2020-11868

7.5 HIGH

📋 TL;DR

This vulnerability in ntpd allows an off-path attacker to spoof NTP server responses and block time synchronization for unauthenticated clients. It affects systems running vulnerable versions of ntp before 4.2.8p14 or 4.3.x before 4.3.100. The attack requires network access but no authentication.

💻 Affected Systems

Products:
  • ntp
  • ntpd
Versions: ntp before 4.2.8p14, 4.3.x before 4.3.100
Operating Systems: Linux, Unix-like systems, Windows (if using ntp)
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects unauthenticated NTP synchronization. Systems using authenticated NTP (autokey or symmetric key) are not vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Time synchronization completely disrupted across an organization, causing authentication failures, log corruption, and service disruptions due to time drift.

🟠

Likely Case

Targeted disruption of time synchronization for specific systems, potentially causing authentication issues and log inconsistencies.

🟢

If Mitigated

Minimal impact if NTP authentication is enabled or systems are patched; time synchronization continues normally.

🌐 Internet-Facing: MEDIUM - Attackers can spoof NTP responses from external servers, but requires specific timing and network position.
🏢 Internal Only: LOW - Internal attackers would need to be on-path or have network control to exploit effectively.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploit requires off-path position and ability to spoof NTP server responses. Proof of concept exists in security advisories.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: ntp 4.2.8p14, ntp 4.3.100

Vendor Advisory: http://support.ntp.org/bin/view/Main/NtpBug3592

Restart Required: Yes

Instructions:

1. Check current ntp version. 2. Update using package manager: 'apt-get update && apt-get upgrade ntp' (Debian/Ubuntu) or 'yum update ntp' (RHEL/CentOS). 3. Restart ntpd service: 'systemctl restart ntpd' or 'service ntp restart'.

🔧 Temporary Workarounds

Enable NTP authentication

linux

Configure NTP authentication using autokey or symmetric keys to prevent spoofed responses

# Edit /etc/ntp.conf
# Add: server ntp.server.com key 10
# Add: keys /etc/ntp.keys
# Generate keys: ntp-keygen
# Restart: systemctl restart ntpd

Restrict NTP sources

linux

Configure firewall rules to only allow NTP from trusted sources

# iptables -A INPUT -p udp --dport 123 -s trusted.ntp.server -j ACCEPT
# iptables -A INPUT -p udp --dport 123 -j DROP

🧯 If You Can't Patch

  • Enable NTP authentication to prevent spoofed responses
  • Implement network segmentation and firewall rules to restrict NTP traffic to trusted sources only

🔍 How to Verify

Check if Vulnerable:

Check ntp version: 'ntpd --version' or 'dpkg -l | grep ntp' or 'rpm -qa | grep ntp'. If version is before 4.2.8p14 or 4.3.100, system is vulnerable.

Check Version:

ntpd --version 2>&1 | head -1

Verify Fix Applied:

Verify updated version: 'ntpd --version' should show 4.2.8p14 or 4.3.100+. Check NTP synchronization: 'ntpq -p' should show proper time sources.

📡 Detection & Monitoring

Log Indicators:

  • NTP log entries showing synchronization failures
  • Unexpected NTP server responses in logs
  • Time drift alerts in system logs

Network Indicators:

  • Spoofed NTP packets with invalid timestamps
  • Unusual NTP traffic patterns from unexpected sources

SIEM Query:

source="ntp.log" AND ("synchronization lost" OR "invalid timestamp" OR "server unreachable")

🔗 References

📤 Share & Export