CVE-2010-0294: chronyd in Chrony before 1.23.1, and possibly 1.24-pre1, generates a syslog message for each unauthorized c...

Security readout for executives and security teams

Chrony’s chronyd daemon could write a syslog entry for every unauthorized command-monitoring packet. An attacker sending many invalid packets could fill disk space through logs, causing service or system disruption. The bundle identifies Chrony before 1.23.1, and possibly 1.24-pre1, but provides no CVSS score. Exposure is most likely where old Chrony versions run and chronyd’s command-monitoring traffic is reachable from untrusted networks. Modern supported distributions are less likely exposed, but legacy appliances, frozen server images, or unmanaged NTP infrastructure should be checked. Treat this as a legacy infrastructure hardening issue, not a confirmed emergency. Prioritize internet-exposed or operationally critical time-sync systems first because disk exhaustion can disrupt dependent services. Mitigation focus: Upgrade Chrony to 1.23.1 or a vendor-supported fixed package.; Review Debian, Chrony, and distribution advisories for package-specific fixes.; Restrict chronyd command-monitoring access to trusted management networks..

Prepared

Jun 28, 2026, 03:36 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.