Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1397331 - (CVE-2016-7431) CVE-2016-7431 ntp: Zero Origin timestamp regression
CVE-2016-7431 ntp: Zero Origin timestamp regression
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20161121,repor...
: Security
Depends On:
Blocks: 1397349
  Show dependency tree / graph
 
Reported: 2016-11-22 05:37 EST by Adam Mariš
Modified: 2016-12-06 10:12 EST (History)
5 users (show)

See Also:
Fixed In Version: ntp-4.2.8p9
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-24 09:21:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Adam Mariš 2016-11-22 05:37:07 EST 
Zero Origin timestamp problems were fixed by Bug 2945 in ntp-4.2.8p6. However, subsequent timestamp validation checks introduced a regression in the handling of some Zero origin timestamp checks.

External References:

http://support.ntp.org/bin/view/Main/NtpBug3102
Comment 1 Adam Mariš 2016-11-22 06:09:23 EST 
Created ntp tracking bugs for this issue:

Affects: fedora-all [bug 1397351]
Comment 3 Adam Mariš 2016-11-24 09:21:20 EST 
Statement:

This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6 and 7.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.