Anonymization by Anonymouse.org ~ Adverts
Anonymouse better ad-free, faster and with encryption?
When we discover a security vulnerability in NTP we follow our Phased Vulnerability Process which includes first notifying Institutional members of the NTP Consortium at Network Time Foundation, then CERT, and finally making a public announcement.
Institutional Members receive advanced notification of security vulnerabilities.
When security patches are ready, they are first given to Premier and Partner Institutional members of the NTP Consortium at Network Time Foundation, then access instructions are provided to CERT, and finally the public release is made on the embargo date.
Premier and Partner Members receive early access to security patches.
If you find a security vulnerability in the NTP codebase, please report it by PGP-encrypted email to the NTF Security Officer Team. You can use our NTF Security Officer PGP Key. Please refrain from discussing potential security issues in any mailing lists or public forums.
NOTE: Non-code vulnerabilities (such as a website issue) should instead be reported to webmaster. Issues for subdomains of "pool.ntp.org" should be reported to the NTP Pool Project.
The following releases provided fixes for at least one security vulnerability. The table for each release provides an entry for each security issue (click its hyperlink to read the details for the vulnerability), indicates the issue’s severity, and provides the dates of advance notification to institutional members, advance release to premier and partner institutional members, and public release.
Refer to the Release Timeline for a complete list of all releases, their public release dates, release announcements, and changelogs.
No security fixes in this release.
No security fixes in this release.
| Security Issue | Severity |
|---|---|
| 3661: Memory leak with CMAC keys | MEDIUM |
| Security Issue | Severity |
|---|---|
| 3565: Crafted null dereference attack from a trusted source with an authenticated mode 6 packet | MEDIUM |
| Security Issue | Severity |
|---|---|
3505: NTPQ/NTPDC: Buffer Overflow in openhost() |
LOW |
| 3012: Sybil vulnerability: ephemeral association attack | LOW/MEDIUM |
Public Release: 2016 Jun 02
| Security Issue | Severity |
|---|---|
3046: CRYPTO_NAK crash |
HIGH |
| 3045: Bad authentication demobilizes ephemeral associations | LOW |
| 3044: Processing spoofed server packets | LOW |
| 3043: Autokey association reset | LOW |
| 3042: Broadcast interleave | LOW |
| Security Issue | Severity |
|---|---|
| 2956: Small-step/big-step | MEDIUM |
| Security Issue | Severity |
|---|---|
| 2853: ntpd control message crash: Crafted NUL-byte in configuration directive | LOW |
| Security Issue | Severity |
|---|---|
| 2781: Authentication doesn’t protect symmetric associations against DoS attacks | MEDIUM |
| 2779: ntpd accepts unauthenticated packets with symmetric key crypto | LOW |
| Security Issue | Severity |
|---|---|
| 2670: receive(): missing return on error | MEDIUM |
| 2669: Buffer overflow in configure() | HIGH |
| 2668: Buffer overflow in ctl_putdata() | HIGH |
| 2667: Buffer overflow in crypto_recv() | HIGH |
| Security Issue | Severity |
|---|---|
| 2666: non-cryptographic random number generator with weak seed used by ntp-keygen to generate symmetric keys | HIGH |
| Security Issue | Severity |
|---|---|
| 1532: DRDoS / Amplification Attack using ntpdc monlist command | MEDIUM |
| Security Issue | Severity |
|---|---|
| 2665 :Weak default key in config_auth() | HIGH |
| Security Issue | Severity |
|---|---|
| 1331: DoS attack from certain NTP mode 7 packets | MEDIUM |
| Security Issue | Severity |
|---|---|
| 1151: Remote exploit if autokey is enabled | MEDIUM |
| Security Issue | Severity |
|---|---|
| Multiple OpenSSL signature verification API misuse | MEDIUM |