First published: Mon Feb 08 2010(Updated: )
The client logging functionality in chronyd in Chrony before 1.23.1 does not restrict the amount of memory used for storage of client information, which allows remote attackers to cause a denial of service (memory consumption) via spoofed (1) NTP or (2) cmdmon packets.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Chrony | =1.19 | |
Chrony | =1.20 | |
Chrony | <=1.23-pre1 | |
Chrony | =1.19.99.3 | |
Chrony | =1.19-1 | |
Chrony | =1.19.99.2 | |
Chrony | =1.21-pre1 | |
Chrony | =1.18 | |
Chrony | =1.24-pre1 | |
Chrony | =1.19.99.1 | |
Chrony | =1.21 | |
<=1.23-pre1 | ||
=1.18 | ||
=1.19 | ||
=1.19-1 | ||
=1.19.99.1 | ||
=1.19.99.2 | ||
=1.19.99.3 | ||
=1.20 | ||
=1.21 | ||
=1.21-pre1 | ||
=1.24-pre1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-0293 is classified as a denial of service vulnerability due to potential memory consumption by malicious packets.
To fix CVE-2010-0293, upgrade Chrony to version 1.23.1 or later, which addresses the memory restriction issue.
CVE-2010-0293 affects various versions of Chrony, specifically versions below 1.23.1, including 1.18, 1.19, 1.20, and intermediate releases.
Yes, CVE-2010-0293 can be exploited remotely by sending spoofed NTP or cmdmon packets to the Chrony client.
CVE-2010-0293 can lead to denial of service, causing the Chrony service to consume excessive memory and potentially crash.