CVE-2014-9294: Weak RNG
As per upstream NTP security advisory:
Prior to ntp-4.2.7p230 ntp-keygen used a weak seed to prepare a random number generator that was of good quality back in the late 1990s. The random numbers produced was then used to generate symmetric keys. In ntp-4.2.8 we use a current-technology cryptographic random number generator, either RANDbytes from OpenSSL, or arc4random().
Mitigation: Upgrade to 4.2.7p230 or later.
This vulnerability was discovered in ntp-4.2.6 by Stephen Roettger of the Google Security Team.
Other sources
util/ntp-keygen.c in ntp-keygen in NTP before 4.2.7p230 uses a weak RNG seed, which makes it easier for remote attackers to defeat cryptographic protection mechanisms via a brute-force attack.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2014-9294?
CVE-2014-9294 is considered to have a moderate severity level due to its impact on cryptographic key generation.
How do I fix CVE-2014-9294?
To fix CVE-2014-9294, update the NTP software to version 4.2.8 or later.
What software is affected by CVE-2014-9294?
CVE-2014-9294 affects NTP versions prior to 4.2.8.
What is the risk of using NTP versions prior to 4.2.8 in relation to CVE-2014-9294?
Using NTP versions prior to 4.2.8 poses a risk of compromising security due to the use of weak random number generation for cryptographic keys.
Can I continue to use older versions of NTP if I apply other security measures for CVE-2014-9294?
It is not recommended to continue using older versions of NTP even with additional security measures due to inherent vulnerabilities like CVE-2014-9294.