Skip to content
Fencer Vulns
critical 9.1

CVE-2019-6444 in the critical feed json

An issue was discovered in NTPsec before 1.1.3.

published 2019-01-16 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-16005

cvss
9.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
45.7%
EPSS 45.7% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB

Summary

An issue was discovered in NTPsec before 1.1.3. process_control() in ntp_control.c has a stack-based buffer over-read because attacker-controlled data is dereferenced by ntohl() in ntpd.

Patch / fix

  • ntpsec ntpsec 1.1.3
  • ntpsec Debian 14, Debian 13, Debian 12 1.1.3+dfsg1-1

debian advisories DEBIAN-CVE-2019-6444

  • ntpsec Ubuntu 18.04 LTS 1.1.0+dfsg1-1ubuntu0.2

ubuntu advisories UBUNTU-CVE-2019-6444

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • ntpsec Alpine 3.24, Alpine 3.23, Alpine 3.22 +12 more 1.1.3-r0

alpine advisories ALPINE-CVE-2019-6444

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Timeline

  1. First public exploit (EDB-46176)
  2. Published

Exploit prediction

45.72% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-46176 NTPsec 1.1.2 - 'ntp_control' Out-of-Bounds Read (PoC) dos, 2019-01-16
  • dumpco.re https://dumpco.re/bugs/ntpsec-oobread2 referenced PoC, tagged "exploit" by a source, unverified
  • dumpco.re https://dumpco.re/blog/ntpsec-bugs referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:N/A:P

Classification

Weakness

References

Sources

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.