First published: Fri Dec 19 2014(Updated: )
As per upstream NTP security advisory: Code in ntp_proto.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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/ntp | <4.2.8 | 4.2.8 |
NTP | <=4.2.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-9296 is classified as a low severity vulnerability because it does not affect system integrity.
To fix CVE-2014-9296, upgrade to NTP version 4.2.8 or later.
CVE-2014-9296 may allow error processing to continue unexpectedly, but it has not been found to compromise system integrity.
CVE-2014-9296 affects NTP versions up to and including 4.2.7.
CVE-2014-9296 does not have a defined remote exploit mechanism due to its nature.