The following flaw was found in NTP: An attacker can send a spoofed packet with an invalid MAC or crypto-NAK to a client/peer and reset its association if it's using autokey for authentication. If this can be done often enough, it will prevent that association from working.
Acknowledgments: Name: Miroslav Lichvar (Red Hat)
Created ntp tracking bugs for this issue: Affects: fedora-all [bug 1342128]
Upstream bug: http://support.ntp.org/bin/view/Main/NtpBug3043 External References: http://support.ntp.org/bin/view/Main/SecurityNotice#June_2016_ntp_4_2_8p8_NTP_Securi
Could anyone suggest any specific reason of closing the bug without fixing it. Secondly advisory for customers who have these vulnerabilities
(In reply to Harkanwal from comment #4) > Could anyone suggest any specific reason of closing the bug without fixing > it. Secondly advisory for customers who have these vulnerabilities Hi, this issue was rated as having a Low security impact. It only affects clients that use autokey authentication, which has various known security problems by itself. Taking this into consideration, the issue is not planned to be fixed. We may revisit this issue in a future minor RHEL release.
ntp-4.2.6p5-41.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
ntp-4.2.6p5-41.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
ntp-4.2.6p5-41.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Mitigation: Disable autokey authentication. Instead, configure ntp to use symmetric key authentication, or no authentication at all (if not required). To configure ntp with symmetric key authentication, follow the steps at https://access.redhat.com/solutions/393663