First published: Fri Jan 27 2017(Updated: )
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.
Credit: cret@cert.org
Affected Software | Affected Version | How to fix |
---|---|---|
NTP ntp | =4.2.8-p3 | |
NTPsec | =a5fb34b9cc89b92a8fef2f459004865c93bb7f92 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-1551 has a medium severity level due to its potential for remote denial of service attacks.
To mitigate CVE-2016-1551, update to a fixed version of NTP or NTPsec that addresses this vulnerability.
NTP 4.2.8p3 and NTPsec version a5fb34b9cc89b92a8fef2f459004865c93bb7f92 are both affected by CVE-2016-1551.
CVE-2016-1551 can allow attackers to impersonate reference clocks, potentially leading to erroneous time synchronization.
Yes, CVE-2016-1551 may be exploited by attackers to manipulate NTP behavior, highlighting the importance of applying fixes.