r1 - 2018-02-28 - 00:18:01 - HarlanStennYou are here: NTP >  Main Web > SecurityNotice > NtpBug3415
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.8p11 was released on 27 February 2018. It addresses 2 low-/medium-, 1 informational-/medium-, and 2 low-severity security issues in ntpd, 1 medium-severity security issue in ntpq, and provides over 65 non-security bugfixes and other improvements over 4.2.8p10.

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 3415

Provide a way to prevent authenticated symmetric passive peering

  • Date Resolved: Stable (4.2.8p11) 27 Feb 2018
  • References: Sec 3415 / CVE-2018-7170 / VU#961909
  • Also See: Sec 3012 / CVE-2016-1549 / VU#718152
  • Affects: All ntp-4 releases up to, but not including 4.2.8p7, and 4.3.0 up to, but not including 4.3.92. Resolved in 4.2.8p11.
  • CVSS2: LOW 3.5 - (AV:N/AC:M/Au:S/C:N/I:P/A:N)
  • CVSS3: LOW 3.1 - (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N)
  • Summary: ntpd can be vulnerable to Sybil attacks. If a system is set up to use a trustedkey and if one is not using the feature introduced in ntp-4.2.8p6 allowing an optional 4th field in the ntp.keys file to specify which IPs can serve time, a malicious authenticated peer -- i.e. one where the attacker knows the private symmetric key -- can create arbitrarily-many ephemeral associations in order to win the clock selection of ntpd and modify a victim's clock. Three additional protections are offered in ntp-4.2.8p11. One is the new noepeer directive, which disables symmetric passive ephemeral peering. Another is the new ippeerlimit directive, which limits the number of peers that can be created from an IP. The third extends the functionality of the 4th field in the ntp.keys file to include specifying a subnet range.
  • Mitigation:
    • Implement BCP-38.
    • Upgrade to ntp-4.2.8p11 or later from the NTP Project Download Page or the NTP Public Services Project Download Page.
    • Use the noepeer directive to prohibit symmetric passive ephemeral associations.
    • Use the ippeerlimit directive to limit the number of peers that can be created from an IP.
    • Use the 4th argument in the ntp.keys file to limit the IPs and subnets that can be time servers.
    • Have enough sources of time.
    • Properly monitor your ntpd instances.
    • If ntpd stops running, auto-restart it without -g .
  • Credit: This weakness was reported as Bug 3012 by Matthew Van Gundy of Cisco ASIG, and separately by Stefan Moser as Bug 3415.
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
 
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback