CVE-2015-5300
HighSummary
The panic_gate check in NTP before version 4.2.8p5 is only re-enabled after the first change to the system clock greater than 128 milliseconds. This allows remote attackers to set NTP to an arbitrary time when started with the -g option or to alter the time by up to 900 seconds otherwise by responding to an unspecified number of requests from trusted sources.
Risk Assessment
Attackers can manipulate the system time, leading to potential synchronization issues and may cause denial of service by aborting and restarting the NTP service.
Recommendation
It is recommended to update NTP to version 4.2.8p5 or later to eliminate this vulnerability and to monitor and restrict access to trusted sources.
Other vulnerabilities in NTP
See all- CVE-2017-6455High
NTP before 4.2.8p10 and 4.3.x before 4.3.94, when using PPSAPI, allows local users to gain privileges via a DLL in the PPSAPI_DLLS environment variable.
- CVE-2016-7434High
The read_mru_list function in NTP before version 4.2.8p9 allows remote attackers to cause a denial of service (crash) via a crafted mrulist query.
- CVE-2015-7974High
NTP versions 4.x before 4.2.8p6 and 4.3.x before 4.3.90 do not verify peer associations of symmetric keys when authenticating packets, which might allow remote attackers to conduct impersonation attacks via an arbitrary trusted key, known as a 'skeleton key.'
Original NVD description (English source)
The panic_gate check in NTP before 4.2.8p5 is only re-enabled after the first change to the system clock that was greater than 128 milliseconds by default, which allows remote attackers to set NTP to an arbitrary time when started with the -g option, or to alter the time by up to 900 seconds otherwise by responding to an unspecified number of requests from trusted sources, and leveraging a resulting denial of service (abort and restart).