Skip to content
OpenAdvisories
Unscored SUSE-SU-2016:1175-1 12 CVEs

Security update for ntp

Published Apr 28, 2016 · Updated Feb 4, 2026

Summary

ntp was updated to version 4.2.8p6 to fix 12 security issues.

These security issues were fixed:
- CVE-2015-8158: Fixed potential infinite loop in ntpq (bsc#962966).
- CVE-2015-8138: Zero Origin Timestamp Bypass (bsc#963002).
- CVE-2015-7979: Off-path Denial of Service (DoS) attack on authenticated broadcast mode (bsc#962784).
- CVE-2015-7978: Stack exhaustion in recursive traversal of restriction list (bsc#963000).
- CVE-2015-7977: reslist NULL pointer dereference (bsc#962970).
- CVE-2015-7976: ntpq saveconfig command allows dangerous characters in filenames (bsc#962802).
- CVE-2015-7975: nextvar() missing length check (bsc#962988).
- CVE-2015-7974: Skeleton Key: Missing key check allows impersonation between authenticated peers (bsc#962960).
- CVE-2015-7973: Replay attack on authenticated broadcast mode (bsc#962995).
- CVE-2015-8140: ntpq vulnerable to replay attacks (bsc#962994).
- CVE-2015-8139: Origin Leak: ntpq and ntpdc, disclose origin (bsc#962997).
- CVE-2015-5300: MITM attacker could have forced ntpd to make a step larger than the panic threshold (bsc#951629).

These non-security issues were fixed:
- fate#320758 bsc#975981: Enable compile-time support for MS-SNTP
(--enable-ntp-signd). This replaces the w32 patches in 4.2.4 that added
the authreg directive.
- bsc#962318: Call /usr/sbin/sntp with full path to synchronize in start-ntpd.
When run as cron job, /usr/sbin/ is not in the path, which caused
the synchronization to fail.
- bsc#782060: Speedup ntpq.
- bsc#916617: Add /var/db/ntp-kod.
- bsc#956773: Add ntp-ENOBUFS.patch to limit a warning that might happen quite a lot on loaded systems.
- bsc#951559,bsc#975496: Fix the TZ offset output of sntp during DST.
- Add ntp-fork.patch and build with threads disabled to allow name resolution even when running chrooted.
- bsc#784760: Remove local clock from default configuration

Fixed packages 2

ReleasePackageFixed in
SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 ntp 4.2.8p6-8.2
SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 ntp 4.2.8p6-8.2

Vulnerabilities 12

  • Unscored —

    The panic_gate check in NTP before 4.2.8p5 is only re-enabled after the first change to the system clock that was great…

  • Unscored —

    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 co…

  • Unscored —

    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 pa…

  • Unscored —

    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, …

  • Unscored —

    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 filte…

  • Unscored —

    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 d…

  • Unscored —

    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) vi…

  • Unscored —
    CVE-2015-7979 EPSS 12%

    NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to cause a denial of service (client-server associat…

  • Unscored —

    NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to bypass the origin timestamp validation via a pack…

  • Unscored —

    ntpq in NTP before 4.2.8p7 allows remote attackers to obtain origin timestamps and then impersonate peers via unspecifi…

  • Unscored —

    The ntpq protocol in NTP before 4.2.8p7 allows remote attackers to conduct replay attacks by sniffing the network.

  • Unscored —

    The getresponse function in ntpq in NTP versions before 4.2.8p9 and 4.3.x before 4.3.90 allows remote attackers to caus…

References

  • report
    https://bugzilla.suse.com/782060
  • report
    https://bugzilla.suse.com/784760
  • report
    https://bugzilla.suse.com/916617
  • report
    https://bugzilla.suse.com/951559
  • report
    https://bugzilla.suse.com/951629
  • report
    https://bugzilla.suse.com/956773
  • report
    https://bugzilla.suse.com/962318
  • report
    https://bugzilla.suse.com/962784
  • report
    https://bugzilla.suse.com/962802
  • report
    https://bugzilla.suse.com/962960
  • report
    https://bugzilla.suse.com/962966
  • report
    https://bugzilla.suse.com/962970
  • report
    https://bugzilla.suse.com/962988
  • report
    https://bugzilla.suse.com/962994
  • report
    https://bugzilla.suse.com/962995
  • report
    https://bugzilla.suse.com/962997
  • report
    https://bugzilla.suse.com/963000
  • report
    https://bugzilla.suse.com/963002
  • report
    https://bugzilla.suse.com/975496
  • report
    https://bugzilla.suse.com/975981
  • web
    https://www.suse.com/security/cve/CVE-2015-5300
  • web
    https://www.suse.com/security/cve/CVE-2015-7973
  • web
    https://www.suse.com/security/cve/CVE-2015-7974
  • web
    https://www.suse.com/security/cve/CVE-2015-7975
  • web
    https://www.suse.com/security/cve/CVE-2015-7976
  • web
    https://www.suse.com/security/cve/CVE-2015-7977
  • web
    https://www.suse.com/security/cve/CVE-2015-7978
  • web
    https://www.suse.com/security/cve/CVE-2015-7979
  • web
    https://www.suse.com/security/cve/CVE-2015-8138
  • web
    https://www.suse.com/security/cve/CVE-2015-8139
  • web
    https://www.suse.com/security/cve/CVE-2015-8140
  • web
    https://www.suse.com/security/cve/CVE-2015-8158