The mx4200_send function in the legacy MX4200 refclock in NTP before 4.2.8p10 and 4.3.x before 4.3.94 does not properly handle the return value of the snprintf function, which allows local users to execute arbitrary code via unspecified vectors, which trigger an out-of-bounds memory write.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.8, requiring local system access to exploit with relatively low complexity without requiring user interaction requiring only low-level privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 1 product from ntp organizations running these solutions should prioritize assessment and patching.
First disclosed in 2017, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2017-03-27T17:59:00.523
2025-04-20T01:37:25.860
Deferred
CVSSv3.0: 7.8 (HIGH)
AV:L/AC:L/Au:N/C:P/I:P/A:P
3.9
6.4
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | ntp | ntp | 4.2.8 | Yes |
| Application | ntp | ntp | 4.3.0 | Yes |
| Application | ntp | ntp | 4.3.1 | Yes |
| Application | ntp | ntp | 4.3.2 | Yes |
| Application | ntp | ntp | 4.3.3 | Yes |
| Application | ntp | ntp | 4.3.4 | Yes |
| Application | ntp | ntp | 4.3.5 | Yes |
| Application | ntp | ntp | 4.3.6 | Yes |
| Application | ntp | ntp | 4.3.7 | Yes |
| Application | ntp | ntp | 4.3.8 | Yes |
| Application | ntp | ntp | 4.3.9 | Yes |
| Application | ntp | ntp | 4.3.10 | Yes |
| Application | ntp | ntp | 4.3.11 | Yes |
| Application | ntp | ntp | 4.3.12 | Yes |
| Application | ntp | ntp | 4.3.13 | Yes |
| Application | ntp | ntp | 4.3.14 | Yes |
| Application | ntp | ntp | 4.3.15 | Yes |
| Application | ntp | ntp | 4.3.16 | Yes |
| Application | ntp | ntp | 4.3.17 | Yes |
| Application | ntp | ntp | 4.3.18 | Yes |
| Application | ntp | ntp | 4.3.19 | Yes |
| Application | ntp | ntp | 4.3.20 | Yes |
| Application | ntp | ntp | 4.3.21 | Yes |
| Application | ntp | ntp | 4.3.22 | Yes |
| Application | ntp | ntp | 4.3.23 | Yes |
| Application | ntp | ntp | 4.3.24 | Yes |
| Application | ntp | ntp | 4.3.25 | Yes |
| Application | ntp | ntp | 4.3.26 | Yes |
| Application | ntp | ntp | 4.3.27 | Yes |
| Application | ntp | ntp | 4.3.28 | Yes |
| Application | ntp | ntp | 4.3.29 | Yes |
| Application | ntp | ntp | 4.3.30 | Yes |
| Application | ntp | ntp | 4.3.31 | Yes |
| Application | ntp | ntp | 4.3.32 | Yes |
| Application | ntp | ntp | 4.3.33 | Yes |
| Application | ntp | ntp | 4.3.34 | Yes |
| Application | ntp | ntp | 4.3.35 | Yes |
| Application | ntp | ntp | 4.3.36 | Yes |
| Application | ntp | ntp | 4.3.37 | Yes |
| Application | ntp | ntp | 4.3.38 | Yes |
| Application | ntp | ntp | 4.3.39 | Yes |
| Application | ntp | ntp | 4.3.40 | Yes |
| Application | ntp | ntp | 4.3.41 | Yes |
| Application | ntp | ntp | 4.3.42 | Yes |
| Application | ntp | ntp | 4.3.43 | Yes |
| Application | ntp | ntp | 4.3.44 | Yes |
| Application | ntp | ntp | 4.3.45 | Yes |
| Application | ntp | ntp | 4.3.46 | Yes |
| Application | ntp | ntp | 4.3.47 | Yes |
| Application | ntp | ntp | 4.3.48 | Yes |
| Application | ntp | ntp | 4.3.49 | Yes |
| Application | ntp | ntp | 4.3.50 | Yes |
| Application | ntp | ntp | 4.3.51 | Yes |
| Application | ntp | ntp | 4.3.52 | Yes |
| Application | ntp | ntp | 4.3.53 | Yes |
| Application | ntp | ntp | 4.3.54 | Yes |
| Application | ntp | ntp | 4.3.55 | Yes |
| Application | ntp | ntp | 4.3.56 | Yes |
| Application | ntp | ntp | 4.3.57 | Yes |
| Application | ntp | ntp | 4.3.58 | Yes |
| Application | ntp | ntp | 4.3.59 | Yes |
| Application | ntp | ntp | 4.3.60 | Yes |
| Application | ntp | ntp | 4.3.61 | Yes |
| Application | ntp | ntp | 4.3.62 | Yes |
| Application | ntp | ntp | 4.3.63 | Yes |
| Application | ntp | ntp | 4.3.64 | Yes |
| Application | ntp | ntp | 4.3.65 | Yes |
| Application | ntp | ntp | 4.3.66 | Yes |
| Application | ntp | ntp | 4.3.67 | Yes |
| Application | ntp | ntp | 4.3.68 | Yes |
| Application | ntp | ntp | 4.3.69 | Yes |
| Application | ntp | ntp | 4.3.70 | Yes |
| Application | ntp | ntp | 4.3.71 | Yes |
| Application | ntp | ntp | 4.3.72 | Yes |
| Application | ntp | ntp | 4.3.73 | Yes |
| Application | ntp | ntp | 4.3.74 | Yes |
| Application | ntp | ntp | 4.3.75 | Yes |
| Application | ntp | ntp | 4.3.76 | Yes |
| Application | ntp | ntp | 4.3.77 | Yes |
| Application | ntp | ntp | 4.3.78 | Yes |
| Application | ntp | ntp | 4.3.79 | Yes |
| Application | ntp | ntp | 4.3.80 | Yes |
| Application | ntp | ntp | 4.3.81 | Yes |
| Application | ntp | ntp | 4.3.82 | Yes |
| Application | ntp | ntp | 4.3.83 | Yes |
| Application | ntp | ntp | 4.3.84 | Yes |
| Application | ntp | ntp | 4.3.85 | Yes |
| Application | ntp | ntp | 4.3.86 | Yes |
| Application | ntp | ntp | 4.3.87 | Yes |
| Application | ntp | ntp | 4.3.88 | Yes |
| Application | ntp | ntp | 4.3.89 | Yes |
| Application | ntp | ntp | 4.3.90 | Yes |
| Application | ntp | ntp | 4.3.91 | Yes |
| Application | ntp | ntp | 4.3.92 | Yes |
| Application | ntp | ntp | 4.3.93 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For ntp's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.