{"id":"GHSA-2xpx-vcmq-5f72","revision":"d2f3e37dbdfd4a09b18822619a6e0a5e","records":[{"revision":"d2f3e37dbdfd4a09b18822619a6e0a5e","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"GHSA-2xpx-vcmq-5f72","aliases":["CVE-2024-38528"],"title":"Unlimited number of NTS-KE connections can crash ntpd-rs server","description":"### Summary\nMissing limit for accepted NTS-KE connections allows an unauthenticated remote attacker to crash ntpd-rs when an NTS-KE server is configured. Non NTS-KE server configurations, such as the default ntpd-rs configuration, are unaffected.\n\n### Details\nOperating systems have a limit for the number of open file descriptors (which includes sockets) in a single process, e.g. 1024 on Linux by default. When ntpd-rs is configured as an NTS server, it accepts TCP connections for the NTS-KE service. If the process has reached the descriptor limit and tries to accept a new TCP connection, the accept() system call will return with the EMFILE error and cause ntpd-rs to abort.\n\nA remote attacker can open a large number of parallel TCP connections to the server to trigger this crash. The connections need to be opened quickly enough to avoid the `key-exchange-timeout-ms` timeout (by default 1000 milliseconds).\n\n### Impact\nOnly NTS-KE server configuration are affected. Those without an NTS-KE server configuration such as NTS client only or NTP only configuration are unaffected. For affected configurations the ntpd-rs daemon can made completely unavailable by crashing the service. If ntpd-rs is automatically restarted, an attacker can repeat the attack to prevent ntpd-rs from doing anything useful.\n\n### Workarounds\n- Disable NTS-KE server functionality\n- Increase system resource limits (`RLIMIT_NOFILE`) to make the attack more difficult\n- Lower the `key-exchange-timeout-ms` configuration setting to make the attack more difficult","state":0,"publishedAt":"2024-06-28T21:05:52+00:00","modifiedAt":"2026-09-10T03:50:14.7936951+00:00","affected":[{"ecosystem":"crates.io","name":"ntpd","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.3.1"},{"kind":"fixed","version":"1.1.3"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","score":null,"severity":null},{"system":"CVSS_V4","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://github.com/pendulum-project/ntpd-rs/security/advisories/GHSA-2xpx-vcmq-5f72","https://nvd.nist.gov/vuln/detail/CVE-2024-38528","https://github.com/pendulum-project/ntpd-rs/commit/6049687006ea5b26eeac927964b5fcc80d7bde50","https://github.com/pendulum-project/ntpd-rs"],"sourceUrl":"https://github.com/advisories/GHSA-2xpx-vcmq-5f72","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-2xpx-vcmq-5f72","identifiers":["GHSA-2xpx-vcmq-5f72","CVE-2024-38528"]},"retained":false,"historicalAffected":[]}],"coverage":[]}