from 0, < 1.24-3.1+deb7u4
from 0, < 1.24-3+squeeze3
from 0, < 2.2.1-1
HIGH7.5Chrony before 1.29.1 has traffic amplification in cmdmon protocol
from 0, < 1.29.1-1
MEDIUM6.5chrony before 1.31.1 does not properly protect state variables in authenticated symmetric NTP associations, which allows remote attackers w…
from 0, < 1.30-2
MEDIUM6.0A flaw was found in chrony versions before 3.5.1 when creating the PID file under the /var/run/chrony folder.
from 0, < 3.5.1-1
—chrony before 1.31.1 does not initialize the last "next" pointer when saving unacknowledged replies to command requests, which allows remot…
from 0, < 1.30-2
—chrony - security update
from 0, < 1.24-3.1+deb7u3
—chrony - security update
from 0, < 1.30-2
—chrony - security update
from 0, < 1.24-3+squeeze2
—cmdmon.c in Chrony before 1.29 allows remote attackers to obtain potentially sensitive information from stack memory via vectors related to…
from 0, < 1.29-1
—chrony - several
from 0, < 1.24-3+squeeze1
—chrony - several
from 0, < 1.29-1
—chronyd in Chrony before 1.23.1, and possibly 1.24-pre1, generates a syslog message for each unauthorized cmdmon packet, which allows remot…
from 0, < 1.23-7
—The client logging functionality in chronyd in Chrony before 1.23.1 does not restrict the amount of memory used for storage of client infor…
from 0, < 1.23-7
—chrony - denial of service
from 0, < 1.21z-5+etch1
—chrony - denial of service
from 0, < 1.23-7