Cyber Resilience

CVE-2019-6443

Memory Safety in Ntpsec ≤ 1.1.3

Public PoCHigh EPSSMemory Safety
Published
16 January 2019
Modified
21 November 2024
CVSS Score v3 9.1
Click a component to see what it means
Raw vectorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS Score 0.67 99.2th percentile
Risk Priority 89 floored blend · peak EPSS

Summary

CVE-2019-6443 is a critical-severity Out-of-bounds Read (CWE-125) vulnerability in Ntpsec Ntpsec. Its CVSS base score is 9.1 (Critical).

Operationally, ranked in the top 0.8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

EU & UK References

Vulnerability Data

An issue was discovered in NTPsec before 1.1.3. Because of a bug in ctl_getitem, there is a stack-based buffer over-read in read_sysvars in ntp_control.c in ntpd.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-4012Same product: Ntpsec Ntpsec
CVE-2024-53876Shared CWE-125
CVE-2023-29315Shared CWE-125
CVE-2025-38320Shared CWE-125
CVE-2026-28832Shared CWE-125
CVE-2025-43226Shared CWE-125
CVE-2024-0207Shared CWE-125
CVE-2023-29942Shared CWE-125
CVE-2023-51607Shared CWE-125
CVE-2025-38483Shared CWE-125

Affected Assets

ntpsec
ntpsec
≤ 1.1.3

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.

PR.PS-02 partial match
prevents

Routine patching replaces vulnerable code containing out-of-bounds read flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.

A.8.15 Logging partial match
detects

Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.

prevents

Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.

prevents

Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.

prevents

Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.

prevents

Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.

References