Security Advisory

CVE-2019-6442: NTPsec ntpd Config OOB Write

Last updated:
  • CVE-2019-6442

CVE-2019-6442 is an out-of-bounds write in NTPsec ntpd before 1.1.3: a malformed remote configuration request, signed with a key ntpd accepts, makes the configuration parser write one byte past a buffer. NVD scores it 6.5 because the attacker needs that key. Upgrade to NTPsec 1.1.3 or later, or deny runtime reconfiguration with restrict nomodify.

Vulnerability summary

CVSS base score

6.5

Medium severity

EPSS score (FIRST)

13.7%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2019-6442 · 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 all versions up to and including 1.1.2; 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 1.2.2+dfsg1-1+deb12u1, trixie 1.2.3+dfsg1-8 and forky/sid 1.2.5+dfsg-1 fixed as of 2026-11-19 (Debian security tracker)
Buildroot and Yocto (meta-openembedded) ntpsec packages—Buildroot master and meta-networking master package NTPsec 1.2.6 as of 2026-11-19, which includes the fix; older trees must ship 1.1.3 or later

What does this mean for affected devices?

NVD describes CVE-2019-6442 this way: "An issue was discovered in NTPsec before 1.1.3. An authenticated attacker can write one byte out of bounds in ntpd via a malformed config request, related to config_remotely in ntp_config.c, yyparse in ntp_parser.tab.c, and yyerror in ntp_parser.y." NVD's Primary score is CVSS v3.0 6.5 (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H): network-reachable, low privileges required, high availability impact. The weakness is CWE-787 (out-of-bounds write) and the legacy CVSS v2 score is 4.0. MITRE assigned the ID and published the record on 2019-01-16 without a score of its own (NVD, CVE record).

What does the attacker need?

NTPsec lets an operator change the running configuration with ntpq :config, which sends the new lines in an NTP control (mode 6) request. The reporter's GitLab issue #510, opened on 2018-10-21, shows that an authenticated but malformed config request makes ntpd write out of bounds. The researcher's write-up gives a proof of concept that signs the request with a configured key (key ID 1 in the test setup) and lists all NTPsec versions up to and including 1.1.2 as affected. That precondition is why NVD rates privileges as low rather than none: the attacker has to know a key that ntpd trusts for control requests. NVD scores the impact as availability only (A:H): the daemon that keeps the device's clock can be taken down.

Which versions fix it?

The NTPsec NEWS file lists "CVE-2019-6442: Authenticated OOB write in ntp_parser.y (GitLab #510)" among the security fixes in 1.1.3 of 2019-01-13, together with CVE-2019-6443, CVE-2019-6444 and CVE-2019-6445. The Debian security tracker marks it fixed in unstable from 1.1.3+dfsg1-1 (bug 919513) and in bookworm, trixie and forky/sid.

Which device builds carry NTPsec?

Embedded Linux images can pull NTPsec from Buildroot, whose ntpsec package is at 1.2.6 on master as of 2026-11-19, or from Yocto's meta-networking layer, which carries an ntpsec 1.2.6 recipe. Both are past the fix; an image that reports NTPsec 1.1.2 or older is affected. If a rebuild has to wait, the NTPsec access-control options offer nomodify, which will "Deny ntpq(1) queries which attempt to modify the state of the server (i.e., run time reconfiguration)", and noquery, which denies all ntpq queries without affecting time service. Remove control keys that the device does not need. Our NTP and chrony vulnerabilities guide sets these NTPsec bugs next to the BusyBox ntpd loop CVE-2016-6301 and the chrony pidfile flaw CVE-2020-14367.

CVE-2019-6442 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.13710, the 96.6th percentile, in the 2026-11-18 dataset (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, authenticated attacker can write one byte out of bounds via a malformed config request (config_remotely, yyparse, yyerror); NVD Primary CVSS v3.0 6.5 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, v2 4.0; CWE-787; CPE ntpsec:ntpsec versionEndExcluding 1.1.3; published 2019-01-16; read 2026-11-19. — NVD
  • CVE record: state PUBLISHED, assigner MITRE, published 2019-01-16; no CNA CVSS; checked 2026-11-19. — CVE.org
  • NTPsec NEWS.adoc, 2019-01-13: 1.1.3: CVE-2019-6442 Authenticated OOB write in ntp_parser.y (GitLab #510), with CVE-2019-6443, 6444 and 6445; read 2026-11-19. — NTPsec project NEWS
  • NTPsec GitLab issue #510 'Authenticated out-of-bounds write in ntp_parser.y', opened 2018-10-21, closed: OOB write with an authenticated but malformed config request; read 2026-11-19. — NTPsec GitLab
  • Researcher write-up: affected all ntpsec versions up to and including 1.1.2; discovered and reported 2018-10-21; vendor patch 1.1.3 on 2019-01-13; PoC uses key ID 1; read 2026-11-19. — dumpco.re
  • Debian security tracker: ntpsec fixed in unstable 1.1.3+dfsg1-1, bug 919513; bookworm 1.2.2+dfsg1-1+deb12u1, trixie 1.2.3+dfsg1-8, forky/sid 1.2.5+dfsg-1 fixed; read 2026-11-19. — Debian security tracker
  • Buildroot package/ntpsec/ntpsec.mk on master: NTPSEC_VERSION = 1.2.6; meta-openembedded master has meta-networking/recipes-support/ntpsec/ntpsec_1.2.6.bb; read 2026-11-19. — Buildroot / OpenEmbedded
  • NTPsec access control documentation: nomodify denies ntpq queries which attempt to modify the state of the server (run time reconfiguration); noquery denies ntpq queries, time service not affected; read 2026-11-19. — NTPsec documentation
  • Not in the CISA KEV catalog version 2026.11.18 (1,786 entries), checked 2026-11-19. — CISA KEV
  • EPSS 0.13710, percentile 0.96570, dataset 2026-11-18, read 2026-11-19. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CVE.org record CVE-2019-6442
  3. NTPsec NEWS (1.1.3 security fixes)
  4. NTPsec GitLab issue #510: Authenticated out-of-bounds write in ntp_parser.y
  5. dumpco.re: Authenticated out-of-bounds write in ntpsec
  6. Debian security tracker: CVE-2019-6442
  7. Buildroot ntpsec package
  8. OpenEmbedded meta-networking ntpsec recipe
  9. NTPsec access control commands and options
  10. CISA KEV
  11. FIRST EPSS

Frequently asked questions

Which NTPsec version fixes CVE-2019-6442?

NTPsec 1.1.3, released on 2019-01-13, lists it as fixed together with CVE-2019-6443, CVE-2019-6444 and CVE-2019-6445. Debian fixed it from 1.1.3+dfsg1-1, and current Buildroot and meta-networking ship 1.2.6 (per NTPsec NEWS, the Debian tracker and Buildroot).

Can CVE-2019-6442 be triggered without credentials?

No. The request has to be authenticated with a key that ntpd accepts for control and configuration requests, which is why NVD scores privileges required as low. Applying restrict nomodify to untrusted networks denies runtime reconfiguration queries from them (per NVD, the reporter's write-up and the NTPsec access-control documentation).

What is the impact on a device?

NVD scores availability only: the out-of-bounds write can take ntpd down, so the device stops keeping or serving time until the daemon restarts. Clock loss then affects certificate checks, logs and schedules that depend on correct time (per NVD and our NTP guide).

Is CVE-2019-6442 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.13710, the 96.6th percentile, in the 2026-11-18 dataset, and a public proof of concept exists (per CISA KEV, FIRST EPSS and the researcher's write-up).