ntpd in NTP 4.2.8p3 and NTPsec a5fb34b9cc89b92a8fef2f459004865c93bb7f92 relies on the underlying operating system to protect it from requests that impersonate reference clocks. Because reference clocks are treated like other peers and stored in the same structure, any packet with a source ip address of a reference clock (127.127.1.1 for example) that reaches the receive() function will match that reference clock's peer record and will be treated as a trusted peer. Any system that lacks the typical martian packet filtering which would block these packets is in danger of having its time controlled by an attacker.
Software security is not security software. Here we're concerned with topics like authentication, access control, confidentiality, cryptography, and privilege management.
| Link | Tags |
|---|---|
| http://www.securityfocus.com/bid/88219 | vdb entry third party advisory |
| http://www.talosintelligence.com/reports/TALOS-2016-0132/ | third party advisory |
| http://www.securitytracker.com/id/1035705 | vdb entry |
| http://www.oracle.com/technetwork/topics/security/bulletinapr2016-2952098.html | third party advisory |
| https://security.netapp.com/advisory/ntap-20171004-0002/ | |
| https://security.FreeBSD.org/advisories/FreeBSD-SA-16:16.ntp.asc | vendor advisory |
| https://security.gentoo.org/glsa/201607-15 | vendor advisory |