CVE-2019-6445: ntpsec NULL Pointer Dereference

EPSS trend

Probability

14.08%

Chance of exploitation in the next 30 days

Percentile

97%

Versus all other CVEs

30-day change

0.00 pp

From 14.08% on 19-09-2026

19-09-202619-10-2026

EPSS score

14.08%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

3 found

referenceUnverified
Exploit Reference (dumpco.re)
Maturity: unknown
referenceUnverified
Exploit Reference (dumpco.re)
Maturity: unknown
exploit-databasedoslinuxVerified
NTPsec 1.1.2 - 'ntp_control' (Authenticated) NULL Pointer Dereference (PoC)
Maturity: poc

References

7 links

www.exploit-db.com/exploits/46177/ExploitX Refsource EXPLOIT DBREPORTThird Party AdvisoryVDB Entry
dumpco.re/blog/ntpsec-bugsX Refsource MISCREPORTExploitThird Party Advisory
github.com/ntpsec/ntpsec/blob/NTPsec_1_1_3/NEWSX Refsource MISCREPORTRelease NotesThird Party Advisory
dumpco.re/bugs/ntpsec-authed-npeX Refsource MISCREPORTExploitThird Party Advisory
ubuntu.com/security/CVE-2019-6445REPORT
www.cve.org/CVERecord?id=CVE-2019-6445REPORT
security-tracker.debian.org/tracker/CVE-2019-6445Advisory

Related vulnerabilities

CVE-2021-22212debianntpsec+20.52%5y ago08-06-2021 12:07ntpkeygen can generate keys that ntpd fails to parse. NTPsec 1.2.0 allows ntpkeygen to generate keys with '#' characters. ntpd then either pads, shortens the key, or fails to load these keys entirely, depending on the key type and the placement of the '#'. This results in the administrator not being able to use the keys as expected or the keys are shorter than expected and easier to brute-force, possibly resulting in MITM attacks between ntp clients and ntp servers. For short AES128 keys, ntpd generates a warning that it is padding them.CVE-2016-1551ntp projectntp+32.23%9y ago27-01-2017 17:00ntpd in NTP 4.2.8p3 and NTPsec a5fb34b9cc89b92a8fef2f459004865c93bb7f92 relies on the underlying operating system to protect it from requests that impersonate reference clocks. Because reference clocks are treated like other peers and stored in the same structure, any packet with a source ip address of a reference clock (127.127.1.1 for example) that reaches the receive() function will match that reference clock's peer record and will be treated as a trusted peer. Any system that lacks the typical martian packet filtering which would block these packets is in danger of having its time controlled by an attacker.CVE-2019-6443debianntpsec+266.88%7y ago16-01-2019 05:00An 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.CVE-2019-6444debianntpsec+245.72%7y ago16-01-2019 05:00An 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.CVE-2019-6442debianntpsec+213.71%7y ago16-01-2019 05:00An 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.CVE-2026-18321debianntpsec+50.11%2mo ago31-07-2026 18:04Buffer overflow in NTPsec's Zyfer refclock allows local attacker to crash ntpd

All vulnerabilities inntpsec

CVE-2019-6445: ntpsec NULL Pointer Dereference

Vulnerability summary

Advisory lineage

Timeline

Description

CVSS metrics

EPSS trend

Known exploited

Public exploits

Weaknesses

Affected systems

References