CVE-2014-9296: Medium severity ntp vulnerability
As per upstream NTP security advisory:
Code in ntpproto.c:receive() was missing a 'return;' in the code path where an error was detected, which meant processing did not stop when a specific rare error occurred. We haven't found a way for this bug to affect system integrity. If there is no way to affect system integrity the base CVSS score for this bug is 0. If there is one avenue through which system integrity can be partially affected, the base score becomes a 5. If system integrity can be partially affected via all three integrity metrics, the CVSS base score become 7.5.
This vulnerability was discovered by Stephen Roettger of the Google Security Team.
Mitigation:
Remove or comment out all configuration directives beginning with the crypto keyword in your ntp.conf file.
Other sources
The receive function in ntpproto.c in ntpd in NTP before 4.2.8 continues to execute after detecting a certain authentication error, which might allow remote attackers to trigger an unintended association change via crafted packets.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2014-9296?
CVE-2014-9296 is classified as a low severity vulnerability because it does not affect system integrity.
How do I fix CVE-2014-9296?
To fix CVE-2014-9296, upgrade to NTP version 4.2.8 or later.
What impact does CVE-2014-9296 have on my system?
CVE-2014-9296 may allow error processing to continue unexpectedly, but it has not been found to compromise system integrity.
Which versions of NTP are affected by CVE-2014-9296?
CVE-2014-9296 affects NTP versions up to and including 4.2.7.
Is CVE-2014-9296 exploitable remotely?
CVE-2014-9296 does not have a defined remote exploit mechanism due to its nature.