First published: Wed Jan 20 2016(Updated: )
It was found that when NTP is configured in broadcast mode, an off-path attacker could broadcast packets with bad authentication (wrong key, mismatched key, incorrect MAC, etc) to all clients. The clients, upon receiving the malformed packets, would break the association with the broadcast server. This could cause the time on affected clients to become out of sync over a longer period of time. Upstream patch: <a href="https://github.com/ntp-project/ntp/commit/fe46889f7baa75fc8e6c0fcde87706d396ce1461">https://github.com/ntp-project/ntp/commit/fe46889f7baa75fc8e6c0fcde87706d396ce1461</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/ntp | 1:4.2.8p12+dfsg-4 1:4.2.8p15+dfsg-1 | |
NTP ntp | <=4.2.8 | |
NTP ntp | =4.3.0 | |
NTP ntp | =4.3.1 | |
NTP ntp | =4.3.2 | |
NTP ntp | =4.3.3 | |
NTP ntp | =4.3.4 | |
NTP ntp | =4.3.5 | |
NTP ntp | =4.3.6 | |
NTP ntp | =4.3.7 | |
NTP ntp | =4.3.8 | |
NTP ntp | =4.3.10 | |
NTP ntp | =4.3.11 | |
NTP ntp | =4.3.12 | |
NTP ntp | =4.3.13 | |
NTP ntp | =4.3.14 | |
NTP ntp | =4.3.15 | |
NTP ntp | =4.3.16 | |
NTP ntp | =4.3.17 | |
NTP ntp | =4.3.18 | |
NTP ntp | =4.3.19 | |
NTP ntp | =4.3.20 | |
NTP ntp | =4.3.21 | |
NTP ntp | =4.3.22 | |
NTP ntp | =4.3.23 | |
NTP ntp | =4.3.24 | |
NTP ntp | =4.3.25 | |
NTP ntp | =4.3.26 | |
NTP ntp | =4.3.27 | |
NTP ntp | =4.3.28 | |
NTP ntp | =4.3.29 | |
NTP ntp | =4.3.30 | |
NTP ntp | =4.3.31 | |
NTP ntp | =4.3.32 | |
NTP ntp | =4.3.33 | |
NTP ntp | =4.3.34 | |
NTP ntp | =4.3.35 | |
NTP ntp | =4.3.36 | |
NTP ntp | =4.3.37 | |
NTP ntp | =4.3.38 | |
NTP ntp | =4.3.39 | |
NTP ntp | =4.3.40 | |
NTP ntp | =4.3.41 | |
NTP ntp | =4.3.42 | |
NTP ntp | =4.3.43 | |
NTP ntp | =4.3.44 | |
NTP ntp | =4.3.45 | |
NTP ntp | =4.3.46 | |
NTP ntp | =4.3.47 | |
NTP ntp | =4.3.48 | |
NTP ntp | =4.3.49 | |
NTP ntp | =4.3.50 | |
NTP ntp | =4.3.51 | |
NTP ntp | =4.3.52 | |
NTP ntp | =4.3.53 | |
NTP ntp | =4.3.54 | |
NTP ntp | =4.3.55 | |
NTP ntp | =4.3.56 | |
NTP ntp | =4.3.57 | |
NTP ntp | =4.3.58 | |
NTP ntp | =4.3.59 | |
NTP ntp | =4.3.60 | |
NTP ntp | =4.3.61 | |
NTP ntp | =4.3.62 | |
NTP ntp | =4.3.63 | |
NTP ntp | =4.3.64 | |
NTP ntp | =4.3.65 | |
NTP ntp | =4.3.66 | |
NTP ntp | =4.3.67 | |
NTP ntp | =4.3.68 | |
NTP ntp | =4.3.69 | |
NTP ntp | =4.3.70 | |
NTP ntp | =4.3.71 | |
NTP ntp | =4.3.72 | |
NTP ntp | =4.3.73 | |
NTP ntp | =4.3.74 | |
NTP ntp | =4.3.75 | |
NTP ntp | =4.3.76 | |
NTP ntp | =4.3.77 | |
NTP ntp | =4.3.78 | |
NTP ntp | =4.3.79 | |
NTP ntp | =4.3.80 | |
NTP ntp | =4.3.81 | |
NTP ntp | =4.3.82 | |
NTP ntp | =4.3.83 | |
NTP ntp | =4.3.84 | |
NTP ntp | =4.3.85 | |
NTP ntp | =4.3.86 | |
NTP ntp | =4.3.87 | |
NTP ntp | =4.3.88 | |
NTP ntp | =4.3.89 | |
redhat/ntp | <4.2.8 | 4.2.8 |
Siemens TIM 4R-IE | ||
Siemens TIM 4R-IE DNP3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-7979 is classified as a medium severity vulnerability that allows an off-path attacker to disrupt NTP services.
To fix CVE-2015-7979, upgrade to NTP version 4.2.8p12 or higher.
Affected versions include NTP versions prior to 4.2.8p12 and 4.3.0 to 4.3.79.
CVE-2015-7979 exploits vulnerabilities in NTP's broadcast mode that allow attackers to send malformed packets.
Yes, products like Siemens TIM 4R-IE and TIM 4R-IE DNP3 are impacted by CVE-2015-7979.