rpm package
suse/yast2-ntp-client&distro=SUSE Linux Enterprise Server for SAP Applications 12 SP1
pkg:rpm/suse/yast2-ntp-client&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20Applications%2012%20SP1
Vulnerabilities (12)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2015-5300 | Hig | 7.5 | < 3.1.22-6.2 | 3.1.22-6.2 | Jul 21, 2017 | 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 | |
| CVE-2015-8158 | Med | 5.9 | < 3.1.22-6.2 | 3.1.22-6.2 | Jan 30, 2017 | The getresponse function in ntpq in NTP versions before 4.2.8p9 and 4.3.x before 4.3.90 allows remote attackers to cause a denial of service (infinite loop) via crafted packets with incorrect values. | |
| CVE-2015-8140 | Med | 4.8 | < 3.1.22-6.2 | 3.1.22-6.2 | Jan 30, 2017 | The ntpq protocol in NTP before 4.2.8p7 allows remote attackers to conduct replay attacks by sniffing the network. | |
| CVE-2015-8139 | Med | 5.3 | < 3.1.22-6.2 | 3.1.22-6.2 | Jan 30, 2017 | ntpq in NTP before 4.2.8p7 allows remote attackers to obtain origin timestamps and then impersonate peers via unspecified vectors. | |
| CVE-2015-8138 | Med | 5.3 | < 3.1.22-6.2 | 3.1.22-6.2 | Jan 30, 2017 | NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to bypass the origin timestamp validation via a packet with an origin timestamp set to zero. | |
| CVE-2015-7979 | Hig | 7.5 | < 3.1.22-6.2 | 3.1.22-6.2 | Jan 30, 2017 | NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to cause a denial of service (client-server association tear down) by sending broadcast packets with invalid authentication to a broadcast client. | |
| CVE-2015-7978 | Hig | 7.5 | < 3.1.22-6.2 | 3.1.22-6.2 | Jan 30, 2017 | NTP before 4.2.8p6 and 4.3.0 before 4.3.90 allows a remote attackers to cause a denial of service (stack exhaustion) via an ntpdc relist command, which triggers recursive traversal of the restriction list. | |
| CVE-2015-7977 | Med | 5.9 | < 3.1.22-6.2 | 3.1.22-6.2 | Jan 30, 2017 | ntpd in NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to cause a denial of service (NULL pointer dereference) via a ntpdc reslist command. | |
| CVE-2015-7976 | Med | 4.3 | < 3.1.22-6.2 | 3.1.22-6.2 | Jan 30, 2017 | The ntpq saveconfig command in NTP 4.1.2, 4.2.x before 4.2.8p6, 4.3, 4.3.25, 4.3.70, and 4.3.77 does not properly filter special characters, which allows attackers to cause unspecified impact via a crafted filename. | |
| CVE-2015-7975 | Med | 6.2 | < 3.1.22-6.2 | 3.1.22-6.2 | Jan 30, 2017 | The nextvar function in NTP before 4.2.8p6 and 4.3.x before 4.3.90 does not properly validate the length of its input, which allows an attacker to cause a denial of service (application crash). | |
| CVE-2015-7973 | Med | 6.5 | < 3.1.22-6.2 | 3.1.22-6.2 | Jan 30, 2017 | NTP before 4.2.8p6 and 4.3.x before 4.3.90, when configured in broadcast mode, allows man-in-the-middle attackers to conduct replay attacks by sniffing the network. | |
| CVE-2015-7974 | Hig | 7.7 | < 3.1.22-6.2 | 3.1.22-6.2 | Jan 26, 2016 | NTP 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, aka a "skeleton key." |
- affected < 3.1.22-6.2fixed 3.1.22-6.2
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
- affected < 3.1.22-6.2fixed 3.1.22-6.2
The getresponse function in ntpq in NTP versions before 4.2.8p9 and 4.3.x before 4.3.90 allows remote attackers to cause a denial of service (infinite loop) via crafted packets with incorrect values.
- affected < 3.1.22-6.2fixed 3.1.22-6.2
The ntpq protocol in NTP before 4.2.8p7 allows remote attackers to conduct replay attacks by sniffing the network.
- affected < 3.1.22-6.2fixed 3.1.22-6.2
ntpq in NTP before 4.2.8p7 allows remote attackers to obtain origin timestamps and then impersonate peers via unspecified vectors.
- affected < 3.1.22-6.2fixed 3.1.22-6.2
NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to bypass the origin timestamp validation via a packet with an origin timestamp set to zero.
- affected < 3.1.22-6.2fixed 3.1.22-6.2
NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to cause a denial of service (client-server association tear down) by sending broadcast packets with invalid authentication to a broadcast client.
- affected < 3.1.22-6.2fixed 3.1.22-6.2
NTP before 4.2.8p6 and 4.3.0 before 4.3.90 allows a remote attackers to cause a denial of service (stack exhaustion) via an ntpdc relist command, which triggers recursive traversal of the restriction list.
- affected < 3.1.22-6.2fixed 3.1.22-6.2
ntpd in NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to cause a denial of service (NULL pointer dereference) via a ntpdc reslist command.
- affected < 3.1.22-6.2fixed 3.1.22-6.2
The ntpq saveconfig command in NTP 4.1.2, 4.2.x before 4.2.8p6, 4.3, 4.3.25, 4.3.70, and 4.3.77 does not properly filter special characters, which allows attackers to cause unspecified impact via a crafted filename.
- affected < 3.1.22-6.2fixed 3.1.22-6.2
The nextvar function in NTP before 4.2.8p6 and 4.3.x before 4.3.90 does not properly validate the length of its input, which allows an attacker to cause a denial of service (application crash).
- affected < 3.1.22-6.2fixed 3.1.22-6.2
NTP before 4.2.8p6 and 4.3.x before 4.3.90, when configured in broadcast mode, allows man-in-the-middle attackers to conduct replay attacks by sniffing the network.
- affected < 3.1.22-6.2fixed 3.1.22-6.2
NTP 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, aka a "skeleton key."