NTP BUG 2902: Configuration directives to change pidfile and driftfile should only be allowed locally
Last update: April 22, 2024 18:49 UTC (7e7bd5857)
Summary
Description
If ntpd is configured to allow for remote configuration, and if the (possibly spoofed) source IP address is allowed to send remote configuration requests, and if the attacker knows the remote configuration password, it’s possible for an attacker to use the pidfile or driftfile directives to potentially overwrite other files.
Mitigation
- Implement BCP-38.
- Upgrade to 4.2.8p4 or later.
- If you cannot upgrade, don’t enable remote configuration.
- If you must enable remote configuration and cannot upgrade, remote configuration of NTF’s
ntpd requires:
- an explicitly configured
trustedkey, and you should also configure a controlkey.
- access from a permitted IP. You choose the IPs.
- authentication. Don’t disable it. Practice secure key safety.
- Monitor your
ntpd instances.
Credit
This weakness was discovered by Miroslav Lichvar of Red Hat.
Timeline