CVE-2015-7976
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...
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Exploit likelihood
What each source reports
NVD Score used
4.3
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.
- Record
CVE-2015-7976- CVSS 3.0
- 4.3 Medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N - CVSS 2.0
- 4.0 Medium
AV:N/AC:L/Au:S/C:N/I:P/A:N - Weakness
- CWE-254
- Updated
- 2026-11-02
CVE List No score
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.
- Record
CVE-2015-7976- Updated
- 2026-11-02
EUVDEUVD-2015-7873 No score
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.
- Record
EUVD-2015-7873- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-gh77-qwr7-pqm7
4.3
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...
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.
- Record
GHSA-gh77-qwr7-pqm7- CVSS 3.0
- 4.3 Medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
OSV
4.3
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.
- Record
CVE-2015-7976- CVSS 3.0
- 4.3 Medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
OSVDEBIAN-CVE-2015-7976
4.3
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.
- Record
DEBIAN-CVE-2015-7976- CVSS 3.0
- 4.3 Medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
Show 7 moreShow less
OSVUBUNTU-CVE-2015-7976
4.3
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.
- Record
UBUNTU-CVE-2015-7976- CVSS 3.0
- 4.3 Medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10181-1 No score
ntp-4.2.8p9-1.1 on GA media
These are all security issues fixed in the ntp-4.2.8p9-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10181-1- Updated
- 2026-11-02
OSVSUSE-SU-2016:1175-1 No score
Security update for ntp
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
- Record
SUSE-SU-2016:1175-1- Updated
- 2026-11-02
OSVSUSE-SU-2016:1177-1 No score
Security update for ntp
ntp was updated to version 4.2.8p6 to fix 12 security issues.
Also yast2-ntp-client was updated to match some sntp syntax changes. (bsc#937837)
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.
- Record
SUSE-SU-2016:1177-1- Updated
- 2026-11-02
OSVSUSE-SU-2016:1247-1 No score
Security update for ntp
ntp was updated to version 4.2.8p6 to fix 28 security issues.
Major functional changes:
- The 'sntp' commandline tool changed its option handling in a major way, some options have been renamed or dropped.
- 'controlkey 1' is added during update to ntp.conf to allow sntp to work.
- The local clock is being disabled during update.
- ntpd is no longer running chrooted.
Other functional changes:
- ntp-signd is installed.
- 'enable mode7' can be added to the configuration to allow ntdpc to work as compatibility mode option.
- 'kod' was removed from the default restrictions.
- SHA1 keys are used by default instead of MD5 keys.
Also yast2-ntp-client was updated to match some sntp syntax changes. (bsc#937837)
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).
- CVE-2015-7871: NAK to the Future: Symmetric association authentication bypass via crypto-NAK (bsc#951608).
- CVE-2015-7855: decodenetnum() will ASSERT botch instead of returning FAIL on some bogus values (bsc#951608).
- CVE-2015-7854: Password Length Memory Corruption Vulnerability (bsc#951608).
- CVE-2015-7853: Invalid length data provided by a custom refclock driver could cause a buffer overflow (bsc#951608).
- CVE-2015-7852: ntpq atoascii() Memory Corruption Vulnerability (bsc#951608).
- CVE-2015-7851: saveconfig Directory Traversal Vulnerability (bsc#951608).
- CVE-2015-7850: remote config logfile-keyfile (bsc#951608).
- CVE-2015-7849: trusted key use-after-free (bsc#951608).
- CVE-2015-7848: mode 7 loop counter underrun (bsc#951608).
- CVE-2015-7701: Slow memory leak in CRYPTO_ASSOC (bsc#951608).
- CVE-2015-7703: configuration directives 'pidfile' and 'driftfile' should only be allowed locally (bsc#951608).
- CVE-2015-7704, CVE-2015-7705: Clients that receive a KoD should validate the origin timestamp field (bsc#951608).
- CVE-2015-7691, CVE-2015-7692, CVE-2015-7702: Incomplete autokey data packet length checks (bsc#951608).
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.
- Add a controlkey line to /etc/ntp.conf if one does not already exist to allow runtime configuuration via ntpq.
- bsc#946386: Temporarily disable memlock to avoid problems due to high memory usage during name resolution.
- bsc#905885: Use SHA1 instead of MD5 for symmetric keys.
- Improve runtime configuration:
- Read keytype from ntp.conf
- Don't write ntp keys to syslog. -…
- Record
SUSE-SU-2016:1247-1- Updated
- 2026-11-02
OSVSUSE-SU-2016:1311-1 No score
Security update for ntp
This network time protocol server ntp was updated to 4.2.8p6 to fix the following issues:
Also yast2-ntp-client was updated to match some sntp syntax changes. (bsc#937837)
Major functional changes:
- The 'sntp' commandline tool changed its option handling in a major way.
- 'controlkey 1' is added during update to ntp.conf to allow sntp to work.
- The local clock is being disabled during update.
- ntpd is no longer running chrooted.
Other functional changes:
- ntp-signd is installed.
- 'enable mode7' can be added to the configuration to allow ntdpc to work as compatibility mode option.
- 'kod' was removed from the default restrictions.
- SHA1 keys are used by default instead of MD5 keys.
These security issues were fixed:
- CVE-2015-5219: An endless loop due to incorrect precision to double conversion (bsc#943216).
- 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).
- CVE-2015-7871: NAK to the Future: Symmetric association authentication bypass via crypto-NAK (bsc#951608).
- CVE-2015-7855: decodenetnum() will ASSERT botch instead of returning FAIL on some bogus values (bsc#951608).
- CVE-2015-7854: Password Length Memory Corruption Vulnerability (bsc#951608).
- CVE-2015-7853: Invalid length data provided by a custom refclock driver could cause a buffer overflow (bsc#951608).
- CVE-2015-7852: ntpq atoascii() Memory Corruption Vulnerability (bsc#951608).
- CVE-2015-7851: saveconfig Directory Traversal Vulnerability (bsc#951608).
- CVE-2015-7850: remote config logfile-keyfile (bsc#951608).
- CVE-2015-7849: trusted key use-after-free (bsc#951608).
- CVE-2015-7848: mode 7 loop counter underrun (bsc#951608).
- CVE-2015-7701: Slow memory leak in CRYPTO_ASSOC (bsc#951608).
- CVE-2015-7703: configuration directives 'pidfile' and 'driftfile' should only be allowed locally (bsc#951608).
- CVE-2015-7704, CVE-2015-7705: Clients that receive a KoD should validate the origin timestamp field (bsc#951608).
- CVE-2015-7691, CVE-2015-7692, CVE-2015-7702: Incomplete autokey data packet length checks (bsc#951608).
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.
- Add a controlkey line to /etc/ntp.conf if one does not already exist to allow runtime configuuration via ntpq.
- bsc#946386: Temporarily disable memlock to avoid problems due to high memory usage during name resolution.
- bsc#905885: Use SHA1 instead of MD5 for symmetric keys.
- Improve runtime…
- Record
SUSE-SU-2016:1311-1- Updated
- 2026-11-02
OSVUSN-3096-1 No score
ntp vulnerabilities
Aanchal Malhotra discovered that NTP incorrectly handled authenticated broadcast mode. A remote attacker could use this issue to perform a replay attack. (CVE-2015-7973)
Matt Street discovered that NTP incorrectly verified peer associations of symmetric keys. A remote attacker could use this issue to perform an impersonation attack. (CVE-2015-7974)
Jonathan Gardner discovered that the NTP ntpq utility incorrectly handled memory. An attacker could possibly use this issue to cause ntpq to crash, resulting in a denial of service. This issue only affected Ubuntu 16.04 LTS. (CVE-2015-7975)
Jonathan Gardner discovered that the NTP ntpq utility incorrectly handled dangerous characters in filenames. An attacker could possibly use this issue to overwrite arbitrary files. (CVE-2015-7976)
Stephen Gray discovered that NTP incorrectly handled large restrict lists. An attacker could use this issue to cause NTP to crash, resulting in a denial of service. (CVE-2015-7977, CVE-2015-7978)
Aanchal Malhotra discovered that NTP incorrectly handled authenticated broadcast mode. A remote attacker could use this issue to cause NTP to crash, resulting in a denial of service. (CVE-2015-7979)
Jonathan Gardner discovered that NTP incorrectly handled origin timestamp checks. A remote attacker could use this issue to spoof peer servers. (CVE-2015-8138)
Jonathan Gardner discovered that the NTP ntpq utility did not properly handle certain incorrect values. An attacker could possibly use this issue to cause ntpq to hang, resulting in a denial of service. (CVE-2015-8158)
It was discovered that the NTP cronjob incorrectly cleaned up the statistics directory. A local attacker could possibly use this to escalate privileges. (CVE-2016-0727)
Stephen Gray and Matthew Van Gundy discovered that NTP incorrectly validated crypto-NAKs. A remote attacker could possibly use this issue to prevent clients from synchronizing. (CVE-2016-1547)
Miroslav Lichvar and Jonathan Gardner discovered that NTP incorrectly handled switching to interleaved symmetric mode. A remote attacker could possibly use this issue to prevent clients from synchronizing. (CVE-2016-1548)
Matthew Van Gundy, Stephen Gray and Loganaden Velvindron discovered that NTP incorrectly handled message authentication. A remote attacker could possibly use this issue to recover the message digest key. (CVE-2016-1550)
Yihan Lian discovered that NTP incorrectly handled duplicate IPs on unconfig directives. An authenticated remote attacker could possibly use this issue to cause NTP to crash, resulting in a denial of service. (CVE-2016-2516)
Yihan Lian discovered that NTP incorrectly handled certail peer associations. A remote attacker could possibly use this issue to cause NTP to crash, resulting in a denial of service. (CVE-2016-2518)
Jakub Prokes discovered that NTP incorrectly handled certain spoofed packets. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2016-4954)
Miroslav Lichvar discovered that NTP incorrectly handled certain packets when autokey is enabled. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2016-4955)
Miroslav Lichvar discovered that NTP incorrectly handled certain spoofed broadcast packets. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2016-4956)
In the default installation, attackers would be isolated by the NTP AppArmor profile.
- Record
USN-3096-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
ntpDebian:11 |
before 1:4.2.8p7+dfsg-1 | 1:4.2.8p7+dfsg-1 |
ntpSUSE:Linux Enterprise Server 11 SP4 |
before 4.2.8p6-8.2 | 4.2.8p6-8.2 |
ntpSUSE:Linux Enterprise Server for SAP Applications 11 SP4 |
before 4.2.8p6-8.2 | 4.2.8p6-8.2 |
ntpSUSE:Linux Enterprise Desktop 12 SP1 |
before 4.2.8p6-8.2 | 4.2.8p6-8.2 |
yast2-ntp-clientSUSE:Linux Enterprise Desktop 12 SP1 |
before 3.1.22-6.2 | 3.1.22-6.2 |
yast2-ntp-clientSUSE:Linux Enterprise Software Development Kit 12 SP1 |
before 3.1.22-6.2 | 3.1.22-6.2 |
ntpSUSE:Linux Enterprise Server 12 SP1 |
before 4.2.8p6-8.2 | 4.2.8p6-8.2 |
yast2-ntp-clientSUSE:Linux Enterprise Server 12 SP1 |
before 3.1.22-6.2 | 3.1.22-6.2 |
ntpSUSE:Linux Enterprise Server for SAP Applications 12 SP1 |
before 4.2.8p6-8.2 | 4.2.8p6-8.2 |
yast2-ntp-clientSUSE:Linux Enterprise Server for SAP Applications 12 SP1 |
before 3.1.22-6.2 | 3.1.22-6.2 |
Show 17 moreShow less
| Package | Affected | Fixed |
|---|---|---|
ntpSUSE:Linux Enterprise Desktop 12 |
before 4.2.8p6-46.5.2 | 4.2.8p6-46.5.2 |
yast2-ntp-clientSUSE:Linux Enterprise Desktop 12 |
before 3.1.12.4-8.2 | 3.1.12.4-8.2 |
yast2-ntp-clientSUSE:Linux Enterprise Software Development Kit 12 |
before 3.1.12.4-8.2 | 3.1.12.4-8.2 |
ntpSUSE:Linux Enterprise Server 12 |
before 4.2.8p6-46.5.2 | 4.2.8p6-46.5.2 |
yast2-ntp-clientSUSE:Linux Enterprise Server 12 |
before 3.1.12.4-8.2 | 3.1.12.4-8.2 |
ntpSUSE:Linux Enterprise Server for SAP Applications 12 |
before 4.2.8p6-46.5.2 | 4.2.8p6-46.5.2 |
yast2-ntp-clientSUSE:Linux Enterprise Server for SAP Applications 12 |
before 3.1.12.4-8.2 | 3.1.12.4-8.2 |
ntpSUSE:OpenStack Cloud 5 |
before 4.2.8p6-41.1 | 4.2.8p6-41.1 |
ntpSUSE:Manager 2.1 |
before 4.2.8p6-41.1 | 4.2.8p6-41.1 |
ntpSUSE:Manager Proxy 2.1 |
before 4.2.8p6-41.1 | 4.2.8p6-41.1 |
ntpSUSE:Linux Enterprise Server 11 SP2-LTSS |
before 4.2.8p6-41.1 | 4.2.8p6-41.1 |
yast2-ntp-clientSUSE:Linux Enterprise Server 11 SP2-LTSS |
before 2.17.14.1-1.12.1 | 2.17.14.1-1.12.1 |
ntpSUSE:Linux Enterprise Server 11 SP3-LTSS |
before 4.2.8p6-41.1 | 4.2.8p6-41.1 |
ntpSUSE:Linux Enterprise Server 11 SP3-TERADATA |
before 4.2.8p6-41.1 | 4.2.8p6-41.1 |
ntpUbuntu:14.04:LTS |
before 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10, plus listed versions 1:4.2.6.p5+dfsg-3ubuntu21:4.2.6.p5+dfsg-3ubuntu2.14.04.11:4.2.6.p5+dfsg-3ubuntu2.14.04.21:4.2.6.p5+dfsg-3ubuntu2.14.04.31:4.2.6.p5+dfsg-3ubuntu2.14.04.51:4.2.6.p5+dfsg-3ubuntu2.14.04.61:4.2.6.p5+dfsg-3ubuntu2.14.04.71:4.2.6.p5+dfsg-3ubuntu2.14.04.8 |
1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 |
ntpUbuntu:16.04:LTS |
before 1:4.2.8p4+dfsg-3ubuntu5.3, plus listed versions 1:4.2.6.p5+dfsg-3ubuntu81:4.2.6.p5+dfsg-3ubuntu8.11:4.2.6.p5+dfsg-3ubuntu91:4.2.8p4+dfsg-3ubuntu11:4.2.8p4+dfsg-3ubuntu2 Show 5 moreShow less1:4.2.8p4+dfsg-3ubuntu31:4.2.8p4+dfsg-3ubuntu41:4.2.8p4+dfsg-3ubuntu51:4.2.8p4+dfsg-3ubuntu5.11:4.2.8p4+dfsg-3ubuntu5.2 |
1:4.2.8p4+dfsg-3ubuntu5.3 |
ntpopenSUSE:Tumbleweed |
before 4.2.8p9-1.1 | 4.2.8p9-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2015-7976 is a medium vulnerability (CVSS 4.3) in Ntp, published December 31, 2015. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 3.58%, the 89th percentile. Fixed in ntp 1:4.2.8p7+dfsg-1.
References
tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20160127-ntpd
ubuntu.com/usn/USN-3096-1
lists.opensuse.org/opensuse-security-announce/2016-04/msg00060.html
lists.opensuse.org/opensuse-security-announce/2016-07/msg00026.html
securitytracker.com/id/1034782
lists.opensuse.org/opensuse-security-announce/2016-05/msg00038.html
Show 140 moreShow less
kb.cert.org/vuls/id/718152
lists.opensuse.org/opensuse-security-announce/2016-05/msg00020.html
support.ntp.org/bin/view/Main/NtpBug2938
security.netapp.com/advisory/ntap-20171031-0001
lists.opensuse.org/opensuse-security-announce/2016-05/msg00048.html
lists.opensuse.org/opensuse-security-announce/2016-08/msg00042.html
lists.opensuse.org/opensuse-security-announce/2016-04/msg00059.html
security.FreeBSD.org/advisories/FreeBSD-SA-16:09.ntp.asc
bto.bluecoat.com/security-advisory/sa113
lists.opensuse.org/opensuse-updates/2016-05/msg00114.html
security.gentoo.org/glsa/201607-15
nvd.nist.gov/vuln/detail/CVE-2015-7976
github.com/advisories/GHSA-gh77-qwr7-pqm7
security-tracker.debian.org/tracker/CVE-2015-7976
suse.com/support/update/announcement/2016/suse-su-20161175-1
bugzilla.suse.com/782060
bugzilla.suse.com/784760
bugzilla.suse.com/916617
bugzilla.suse.com/951559
bugzilla.suse.com/951629
bugzilla.suse.com/956773
bugzilla.suse.com/962318
bugzilla.suse.com/962784
bugzilla.suse.com/962802
bugzilla.suse.com/962960
bugzilla.suse.com/962966
bugzilla.suse.com/962970
bugzilla.suse.com/962988
bugzilla.suse.com/962994
bugzilla.suse.com/962995
bugzilla.suse.com/962997
bugzilla.suse.com/963000
bugzilla.suse.com/963002
bugzilla.suse.com/975496
bugzilla.suse.com/975981
suse.com/security/cve/CVE-2015-5300
suse.com/security/cve/CVE-2015-7973
suse.com/security/cve/CVE-2015-7974
suse.com/security/cve/CVE-2015-7975
suse.com/security/cve/CVE-2015-7976
suse.com/security/cve/CVE-2015-7977
suse.com/security/cve/CVE-2015-7978
suse.com/security/cve/CVE-2015-7979
suse.com/security/cve/CVE-2015-8138
suse.com/security/cve/CVE-2015-8139
suse.com/security/cve/CVE-2015-8140
suse.com/security/cve/CVE-2015-8158
suse.com/support/update/announcement/2016/suse-su-20161177-1
bugzilla.suse.com/937837
suse.com/support/update/announcement/2016/suse-su-20161247-1
bugzilla.suse.com/905885
bugzilla.suse.com/910063
bugzilla.suse.com/920238
bugzilla.suse.com/926510
bugzilla.suse.com/936327
bugzilla.suse.com/942587
bugzilla.suse.com/944300
bugzilla.suse.com/946386
bugzilla.suse.com/951608
bugzilla.suse.com/954982
suse.com/security/cve/CVE-2015-7691
suse.com/security/cve/CVE-2015-7692
suse.com/security/cve/CVE-2015-7701
suse.com/security/cve/CVE-2015-7702
suse.com/security/cve/CVE-2015-7703
suse.com/security/cve/CVE-2015-7704
suse.com/security/cve/CVE-2015-7705
suse.com/security/cve/CVE-2015-7848
suse.com/security/cve/CVE-2015-7849
suse.com/security/cve/CVE-2015-7850
suse.com/security/cve/CVE-2015-7851
suse.com/security/cve/CVE-2015-7852
suse.com/security/cve/CVE-2015-7853
suse.com/security/cve/CVE-2015-7854
suse.com/security/cve/CVE-2015-7855
suse.com/security/cve/CVE-2015-7871
suse.com/support/update/announcement/2016/suse-su-20161311-1
bugzilla.suse.com/920183
bugzilla.suse.com/942441
bugzilla.suse.com/943216
bugzilla.suse.com/943218
bugzilla.suse.com/951351
suse.com/security/cve/CVE-2015-5194
suse.com/security/cve/CVE-2015-5219
ubuntu.com/security/CVE-2015-7976
support.ntp.org/bin/view/Main/SecurityNotice
talosintel.com/reports/TALOS-2016-0073
ubuntu.com/security/notices/USN-3096-1
cve.org/CVERecord?id=CVE-2015-7976
ubuntu.com/security/CVE-2015-7973
ubuntu.com/security/CVE-2015-7974
ubuntu.com/security/CVE-2015-7975
ubuntu.com/security/CVE-2015-7977
ubuntu.com/security/CVE-2015-7978
ubuntu.com/security/CVE-2015-7979
ubuntu.com/security/CVE-2015-8138
ubuntu.com/security/CVE-2015-8158
ubuntu.com/security/CVE-2016-0727
ubuntu.com/security/CVE-2016-1547
ubuntu.com/security/CVE-2016-1548
ubuntu.com/security/CVE-2016-1550
ubuntu.com/security/CVE-2016-2516
ubuntu.com/security/CVE-2016-2518
ubuntu.com/security/CVE-2016-4954
ubuntu.com/security/CVE-2016-4955
ubuntu.com/security/CVE-2016-4956
suse.com/security/cve/CVE-2009-0159
suse.com/security/cve/CVE-2009-1252
suse.com/security/cve/CVE-2013-5211
suse.com/security/cve/CVE-2014-9293
suse.com/security/cve/CVE-2014-9294
suse.com/security/cve/CVE-2014-9295
suse.com/security/cve/CVE-2014-9296
suse.com/security/cve/CVE-2014-9297
suse.com/security/cve/CVE-2014-9298
suse.com/security/cve/CVE-2015-1798
suse.com/security/cve/CVE-2015-1799
suse.com/security/cve/CVE-2016-1547
suse.com/security/cve/CVE-2016-1548
suse.com/security/cve/CVE-2016-1549
suse.com/security/cve/CVE-2016-1550
suse.com/security/cve/CVE-2016-1551
suse.com/security/cve/CVE-2016-2516
suse.com/security/cve/CVE-2016-2517
suse.com/security/cve/CVE-2016-2518
suse.com/security/cve/CVE-2016-2519
suse.com/security/cve/CVE-2016-4953
suse.com/security/cve/CVE-2016-4954
suse.com/security/cve/CVE-2016-4955
suse.com/security/cve/CVE-2016-4956
suse.com/security/cve/CVE-2016-4957
suse.com/security/cve/CVE-2016-7426
suse.com/security/cve/CVE-2016-7427
suse.com/security/cve/CVE-2016-7428
suse.com/security/cve/CVE-2016-7429
suse.com/security/cve/CVE-2016-7431
suse.com/security/cve/CVE-2016-7433
suse.com/security/cve/CVE-2016-7434
suse.com/security/cve/CVE-2016-9310
suse.com/security/cve/CVE-2016-9311
Left out here: the rest of 2 source descriptions. The JSON record has them.