It was found that ntpd automatically generated weak keys for its internal use if no ntpdc request authentication key was specified in the ntp.conf configuration file. A remote attacker able to match the configured IP restrictions could guess the generated key, and possibly use it to send ntpdc query or configuration requests.
Find out more about CVE-2014-9293 from the MITRE CVE dictionary dictionary and NIST NVD.
| Base Score | 4 |
|---|---|
| Base Metrics | AV:N/AC:H/Au:N/C:P/I:P/A:N |
| Access Vector | Network |
| Access Complexity | High |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | None |
Find out more about Red Hat support for the Common Vulnerability Scoring System (CVSS).
| Platform | Errata | Release Date |
|---|---|---|
| Red Hat Enterprise Linux Extended Update Support 6.5 (ntp) | RHSA-2015:0104 | 2015-01-28 |
| Red Hat Enterprise Linux 5 (ntp) | RHSA-2014:2025 | 2014-12-20 |
| Red Hat Enterprise Linux 7 (ntp) | RHSA-2014:2024 | 2014-12-20 |
| Red Hat Enterprise Linux 6 (ntp) | RHSA-2014:2024 | 2014-12-20 |
Issue these commands to explicitly generate a strong key and add it to the
ntpd configuration:
echo trustedkey 65535 >> /etc/ntp.conf
printf "65535\tM\t%s\n" $(tr -cd a-zA-Z0-9 < /dev/urandom | head -c 16) >> /etc/ntp/keys
The generated key has about 95 bits of entropy.
Vulmon