It was found that the fix for CVE-2016-1548 did not cover broadcast associations; broadcast clients could be triggered to flip into interleave mode and be exposed to the same vulnerability as described in CVE-2016-1548 (bug 1331462).
Acknowledgments: Name: Miroslav Lichvar (Red Hat)
Mitigation: Do not use NTP's broadcast mode in the clients by not configuring the "broadcastclient" directive in the ntp.conf file.
Created ntp tracking bugs for this issue: Affects: fedora-all [bug 1342128]
Upstream bug: http://support.ntp.org/bin/view/Main/NtpBug3042 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 #5) > 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 are configured to use the broadcast mode. Plus, an attacker would need to have access to an ntpd server to trigger the issue on a given client. All of this combined means that this issue is very unlikely to be exloited, and thus 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.