CVE-2017-6459 json
The Windows installer for NTP before 4.2.8p10 and 4.3.x before 4.3.94 allows local users to have unspecified impact via vectors related to…
published 2017-03-27 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-15516
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
The Windows installer for NTP before 4.2.8p10 and 4.3.x before 4.3.94 allows local users to have unspecified impact via vectors related to an argument with multiple null bytes.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-6459 updated cvss 1.8
ntp: Data Structure terminated insufficiently
-
Red Hat Enterprise Linux 5 ntp Red Hat Enterprise Linux 6 ntp, ntpdate, ntp-perl Red Hat Enterprise Linux 7 ntp, sntp, ntpdate, ntp-perlnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
support.ntp.org
/bin/view/Main/NtpBug3382
vendor-advisory
-
support.ntp.org
/bin/view/Main/SecurityNotice#March_2017_ntp_4_2_8p10_NTP_Secu
vendor-advisory
-
securitytracker.com
/id/1038123
vdb-entry, third-party-advisory
- support.apple.com /HT208144
-
securityfocus.com
/bid/97076
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-6459
- NVD CVE-2017-6459
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.