CVE-2015-1853
First published: Mon Dec 09 2019(Updated: )
chrony before 1.31.1 does not properly protect state variables in authenticated symmetric NTP associations, which allows remote attackers with knowledge of NTP peering to cause a denial of service (inability to synchronize) via random timestamps in crafted NTP data packets.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Chrony | <1.31.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2015-1853?
CVE-2015-1853 has a high severity due to its potential to cause denial of service by interrupting NTP synchronization.
How do I fix CVE-2015-1853?
To fix CVE-2015-1853, upgrade Chrony to version 1.31.1 or later, which addresses the vulnerability.
What systems are affected by CVE-2015-1853?
CVE-2015-1853 affects Chrony versions prior to 1.31.1 across various operating systems that utilize NTP.
Can CVE-2015-1853 be exploited remotely?
Yes, CVE-2015-1853 can be exploited remotely by attackers who can craft specific NTP data packets.
What impact does CVE-2015-1853 have on NTP services?
The impact of CVE-2015-1853 includes the inability to synchronize time, leading to potential disruptions in services that rely on accurate timekeeping.
- agent/references
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- agent/severity
- agent/author
- agent/tags
- agent/description
- agent/softwarecombine
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/tuxfamily
- canonical/chrony