NTP users are strongly urged to take immediate action to ensure that their NTP daemons are not susceptible to being used in distributed denial-of-service (DDoS) attacks. Please also take this opportunity to defeat denial-of-service attacks by implementing Ingress and Egress filtering through BCP38.

ntp-4.2.8p15 was released on 23 June 2020. It addresses 1 medium-severity security issue in ntpd, and provides 13 non-security bugfixes over 4.2.8p13.

Please see the NTP Security Notice for vulnerability and mitigation details.

---

Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.

NTP Bug 3387

NTP-01-012 NTP: Authenticated DoS via Malicious Config Option (Medium)

• Date Resolved: 21 Mar 2017
• References: Sec 3387 / CVE-2017-6463 / VU#325339
• Affects: All versions of ntp, up to but not including ntp-4.2.8p10, and ntp-4.3.0 up to, but not including ntp-4.3.94.
• CVSS2: MED 4.6 (AV:N/AC:H/Au:M/C:N/I:N/A:C)
• CVSS3: MED 4.2 CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H
• Summary: A vulnerability found in the NTP server allows an authenticated remote attacker to crash the daemon by sending an invalid setting via the :config directive. The unpeer option expects a number or an address as an argument. In case the value is “0”, a segmentation fault occurs.
• Mitigation:
  • Implement BCP-38.
  • Upgrade to 4.2.8p10, or later, from the NTP Project Download Page or the NTP Public Services Project Download Page
  • Properly monitor your ntpd instances, and auto-restart ntpd (without -g) if it stops running.
• Credit: This weakness was discovered by Cure53.