Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1331469 - (CVE-2016-2519) CVE-2016-2519 ntp: ctl_getitem() return value not always checked
CVE-2016-2519 ntp: ctl_getitem() return value not always checked
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20160426,reported=2...
: Security
Depends On:
Blocks: 1331437
  Show dependency treegraph
 
Reported: 2016-04-28 10:53 EDT by Martin Prpič
Modified: 2016-05-06 15:46 EDT (History)
3 users (show)

See Also:
Fixed In Version: ntp 4.2.8p7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-02 07:49:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Martin Prpič 2016-04-28 10:53:57 EDT
The following flaw was found in ntpd:

ntpq and ntpdc can be used to store and retrieve information in ntpd. It is possible to store a data value that is larger than the size of the buffer that the ctl_getitem() function of ntpd uses to report the return value. If the length of the requested data value returned by ctl_getitem() is too large, the value NULL is returned instead. There are 2 cases where the return value from ctl_getitem() was not directly checked to make sure it's not NULL, but there are subsequent INSIST() checks that make sure the return value is not NULL. There are no data values ordinarily stored in ntpd that would exceed this buffer length. But if one has permission to store values and one stores a value that is "too large", then ntpd will abort if an attempt is made to read that oversized value. 

Upstream bugs:

http://support.ntp.org/bin/view/Main/NtpBug3008

External References:

http://support.ntp.org/bin/view/Main/SecurityNotice#April_2016_NTP_4_2_8p7_Security

Note You need to log in before you can comment on or make changes to this bug.