ntp.org [4.2.8p15/ntpq] Exploit

[PR3MIUM]

ntp.org [4.2.8p15/ntpq] Exploit.

Source:

GitHub - spwpun/ntp-4.2.8p15-cves: 5 cves of ntp 4.2.8p15 founded by me.

5 cves of ntp 4.2.8p15 founded by me. Contribute to spwpun/ntp-4.2.8p15-cves development by creating an account on GitHub.

github.com

CVE-2023-26551, CVE-2023-26552, CVE-2023-26553, CVE-2023-26554, CVE-2023-26555

 

[AndreiV]

ntp.org [4.2.8p15/ntpq] Exploit.

Source:

GitHub - spwpun/ntp-4.2.8p15-cves: 5 cves of ntp 4.2.8p15 founded by me.

5 cves of ntp 4.2.8p15 founded by me. Contribute to spwpun/ntp-4.2.8p15-cves development by creating an account on GitHub.

github.com

CVE-2023-26551, CVE-2023-26552, CVE-2023-26553, CVE-2023-26554, CVE-2023-26555

ntpd is not vulnerable · Issue #1 · spwpun/ntp-4.2.8p15-cves

The first four of these CVEs affect a function in libntp that is only used by ntpq, but not by ntpd. The last CVE affects the driver for a hardware clock (GPS receiver), so ntpd might be vulnerable...

github.com

ntpd is not vulnerable #1 :

The first four of these CVEs affect a function in libntp that is only used by ntpq, but not by ntpd.
The last CVE affects the driver for a hardware clock (GPS receiver), so ntpd might be vulnerable to manipulated devices of that type, but not to remote attacks.

Did you see the guys name and bio? I would wait for professionals to assess this before worrying.

 

[PR3MIUM]

mstolfp in libntp/mstolfp.c in NTP 4.2.8p15 has an out-of-bounds write in the cp<cpdec while loop. An adversary may be able to attack a client ntpq process, but cannot attack ntpd.

NVD - CVE-2023-26551

nvd.nist.gov

Little Fix:

ntpd is not vulnerable · Issue #1 · spwpun/ntp-4.2.8p15-cves

The first four of these CVEs affect a function in libntp that is only used by ntpq, but not by ntpd. The last CVE affects the driver for a hardware clock (GPS receiver), so ntpd might be vulnerable...

github.com