It was reported [1] that ntp allows bypassing source IP ACLs on some OSes when ::1 spoofed. Upstream commits that fixes this: http://bk.ntp.org/ntp-stable/?PAGE=patch&REV=54922b65gDSbE4G7c3JjkuK1Tv33qQ http://bk.ntp.org/ntp-stable/?PAGE=patch&REV=5492d2879rotbnnuVch_ZC3RAfS8AA http://bk.ntp.org/ntp-stable/?PAGE=patch&REV=5496213frLaEz5PHLZVhuYjM7Lalkw [1]: http://bugs.ntp.org/2672
*** Bug 1189410 has been marked as a duplicate of this bug. ***
External References: http://support.ntp.org/bin/view/Main/SecurityNotice#1_can_be_spoofed_on_some_OSes_so
This phenomenon is discussed in the knowledgebase article: https://access.redhat.com/articles/1305723
ntp-4.2.6p5-20.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
ntp-4.2.6p5-27.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
Statement: This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. To mitigate this issue, you may use the ip6tables command to prevent spoofing of local addresses on any network interface other than the loopback interface. Refer to the Mitigation section on our KBase article: https://access.redhat.com/articles/1305723
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2015:1459 https://rhn.redhat.com/errata/RHSA-2015-1459.html
The CVE-2014-9298 (and CVE-2014-9297) was rejected, apparently because of an incorrect use on some unspecified place, where ids were ids were probably swapped. CVE-2014-9751 is now expected to be used for the issue the CVE-2014-9298 previously referred to. This bug report was previously updated to replace rejected CVE id with the new one. However, as the rejected id was already used in a released RHSA and is still the only id listed on the upstream security pages, I'm re-adding the rejected id here. Released RHSA erratum was updated to also list the new CVE id as fixed.
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2015:2231 https://rhn.redhat.com/errata/RHSA-2015-2231.html