Security Advisory

CVE-2019-6443: NTPsec ntpd Mode 6 Over-Read

Last updated:
  • CVE-2019-6443

CVE-2019-6443 is a stack-based buffer over-read (CWE-125) in NTPsec ntpd before 1.1.3: a bug in ctl_getitem lets a crafted NTP control (mode 6) request read past the request buffer in read_sysvars, with no authentication. NVD scores it 9.1. Upgrade to NTPsec 1.1.3 or later, or block control queries with restrict noquery.

Vulnerability summary

CVSS base score

9.1

Critical severity

EPSS score (FIRST)

66.9%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2019-6443 · Source: NVD

Affected components

ComponentCPEVersion range
NTPsec ntpdcpe:2.3:a:ntpsec:ntpsec:*:*:*:*:*:*:*:*Before 1.1.3 per NVD (no lower bound); the reporter lists 1.1.1 and 1.1.2 as affected; fixed in 1.1.3 (NTPsec NEWS)
Debian ntpsec source packagepkg:deb/debian/ntpsecFixed in unstable from 1.1.3+dfsg1-1 (Debian bug 919513); bookworm, trixie and forky/sid fixed as of 2026-11-19 (Debian security tracker)
Buildroot ntpsec package—Buildroot master packages NTPsec 1.2.6 as of 2026-11-19, which includes the fix; older Buildroot trees must ship 1.1.3 or later

What does this mean for affected devices?

NVD describes CVE-2019-6443 this way: "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." NVD's Primary score is CVSS v3.0 9.1 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H), network-reachable with no privileges, high confidentiality and availability impact, and the weakness is CWE-125 (out-of-bounds read). The record was published on 2019-01-16 by MITRE, which assigned no score of its own (NVD, CVE record).

What is the bug in NTPsec's mode 6 handler?

ctl_getitem() parses the variable list in an NTP control (mode 6) request, the protocol ntpq uses to read daemon variables. The reporter's GitLab issue #507 shows the scan loop incrementing its pointer past the end of the request and reading uninitialised stack memory. The researcher's write-up lists NTPsec 1.1.1 and 1.1.2 as affected, gives a single-packet proof of concept that sends a read-variables request, and shows AddressSanitizer stopping ntpd with a stack-buffer-overflow read in ctl_getitem called from read_sysvars. The bug was reported on 2018-10-16 and fixed in the 1.1.3 release.

Which versions fix it, and what else was fixed?

The NTPsec NEWS file lists, under "2019-01-13: 1.1.3", security fixes "for bugs inherited from NTP Classic": CVE-2019-6443 (out-of-bounds read in ctl_getitem()), CVE-2019-6444 (out-of-bounds read in process_control()), CVE-2019-6445 ("Remotely triggerable crash in ntp_control.c") and CVE-2019-6442 (authenticated out-of-bounds write in ntp_parser.y). The researcher's summary lists the same four. NVD's CPE configuration is cpe:2.3:a:ntpsec:ntpsec before 1.1.3 with no lower bound.

Which device builds carry NTPsec?

NTPsec ships in embedded Linux images built with Buildroot, whose ntpsec package is at 1.2.6 on master as of 2026-11-19, well past the fix. The Debian security tracker marks the issue fixed in unstable from 1.1.3+dfsg1-1 (bug 919513), and bookworm (1.2.2+dfsg1-1+deb12u1), trixie and forky/sid as fixed. A device whose image reports NTPsec 1.1.2 or older in ntpd --version or its package list is affected. If a rebuild is not possible, deny control queries from untrusted networks: the NTPsec access-control documentation says restrict ... noquery will "Deny ntpq(1) queries. Time service is not affected." Our NTP and chrony vulnerabilities guide ranks it alongside the ntpd monlist flaw CVE-2013-5211, the BusyBox ntpd loop CVE-2016-6301 and the later NTPsec NTS crash CVE-2023-4012.

CVE-2019-6443 is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18, 1,786 entries). FIRST EPSS gives it 0.6688, the 99.3rd percentile, in the 2026-11-18 dataset, and a public proof of concept exists (CISA KEV, FIRST EPSS).

How to fix this class of issueThis advisory's weakness class is Memory corruption. Our practical guide covers how to detect, fix, verify and disclose it: How to fix memory corruption in embedded firmware.

Evidence

  • NVD: NTPsec before 1.1.3, ctl_getitem bug, stack-based buffer over-read in read_sysvars in ntp_control.c; NVD Primary CVSS v3.0 9.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H (v2 6.4); CWE-125; CPE ntpsec:ntpsec versionEndExcluding 1.1.3; published 2019-01-16; status Modified. — NVD
  • CVE record: state PUBLISHED, assigner MITRE, published 2019-01-16; no CNA CVSS score; references dumpco.re, NTPsec 1.1.3 NEWS and Exploit-DB 46175. — CVE.org
  • NTPsec NEWS.adoc, section 2019-01-13: 1.1.3: security fixes for bugs inherited from NTP Classic: CVE-2019-6443 OOB read in ctl_getitem() (GitLab #507), CVE-2019-6444 OOB read in process_control(), CVE-2019-6445 remotely triggerable crash in ntp_control.c, CVE-2019-6442 authenticated OOB write in ntp_parser.y. — NTPsec project NEWS
  • NTPsec GitLab issue #507 'Out of bounds read in ctl_getitem() in ntp_control.c': loop increments cp out of bounds and dereferences uninitialised data; crash report on 1.1.2. — NTPsec GitLab
  • Researcher write-up: affected ntpsec 1.1.1 and 1.1.2; reported 2018-10-16; vendor patch 1.1.3 on 2019-01-13; ASan stack-buffer-overflow READ in ctl_getitem from read_sysvars; Python proof of concept sending one mode 6 packet. Blog lists the four CVEs fixed in 1.1.3. — dumpco.re
  • Debian security tracker: ntpsec fixed in unstable 1.1.3+dfsg1-1, Debian bug 919513; bookworm 1.2.2+dfsg1-1+deb12u1, trixie 1.2.3+dfsg1-8, forky/sid 1.2.5+dfsg-1 all fixed. — Debian security tracker
  • Buildroot package/ntpsec/ntpsec.mk on master: NTPSEC_VERSION = 1.2.6, read 2026-11-19. — Buildroot
  • NTPsec access control documentation: noquery denies ntpq(1) queries, time service is not affected; the built-in default entry has noquery. — NTPsec documentation
  • Not in the CISA KEV catalog, version 2026.11.18 (1,786 entries), checked 2026-11-19. — CISA KEV
  • EPSS 0.66881, percentile 0.99308, dataset 2026-11-18, read 2026-11-19. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CVE.org record CVE-2019-6443 (assigner: MITRE)
  3. NTPsec NEWS: 1.1.3 release notes with CVE-2019-6442, -6443, -6444, -6445
  4. NTPsec GitLab issue #507: out of bounds read in ctl_getitem()
  5. dumpco.re: out-of-bounds read in ntpsec (CVE-2019-6443)
  6. dumpco.re: ntpsec bugs fixed in 1.1.3
  7. Debian security tracker: CVE-2019-6443
  8. Buildroot: package/ntpsec/ntpsec.mk
  9. NTPsec documentation: access control commands and options
  10. CISA KEV
  11. FIRST EPSS

Frequently asked questions

Which NTPsec version fixes CVE-2019-6443?

NTPsec 1.1.3, released on 2019-01-13, and every later release. NVD lists all NTPsec versions before 1.1.3 as affected; the reporter tested 1.1.1 and 1.1.2. Debian fixed it in unstable from 1.1.3+dfsg1-1 (per the NTPsec NEWS file, NVD and the Debian security tracker).

Does an attacker need credentials to trigger CVE-2019-6443?

No. NVD's vector is AV:N/AC:L/PR:N, and the published proof of concept is a single unauthenticated NTP control (mode 6) read-variables packet. Only devices whose ntpd answers control queries from the attacker's network are reachable (per NVD and the dumpco.re write-up).

How do I mitigate CVE-2019-6443 if I cannot update the firmware's NTPsec?

Deny NTP control queries from untrusted networks with a restrict default noquery line in the NTPsec configuration. The NTPsec documentation says noquery will deny ntpq queries while time service is not affected, so clients keep synchronising. Then plan a rebuild with NTPsec 1.1.3 or later (per the NTPsec access control documentation and NEWS file).

Is CVE-2019-6443 exploited in the wild?

It is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18). FIRST EPSS gives it 0.6688, the 99.3rd percentile, in the 2026-11-18 dataset, and a public proof of concept exists (per CISA KEV, FIRST EPSS and dumpco.re).