CVE-2020-13817

mediumpriority · track · 31OT risk · elevatedEPSS 0.034 · 89 %ileDEEURUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
3.36% (89th) EPSS
CVSS 5.8 · medium
Is it mine?
104 products
Check your exposure
Who says so?
7 sources
cnnvd · enisa_euvd · fstec_bdu · auma_psirt

EPSS · scored 2026-10-22

ntpd in ntp before 4.2.8p14 and 4.3.x before 4.3.100 allows remote attackers to cause a denial of service (daemon exit or system time change) by predicting transmit timestamps for use in spoofed packets. The victim must be relying on unauthenticated IPv4 time sources. There must be an off-path attacker who can query time from the victim's ntpd instance.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

  • Fixedntp-0:4.2.6p5-29.el7_8.2.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-0:4.2.6p5-29.el7_8.2.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-0:4.2.6p5-29.el7_8.2.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-0:4.2.6p5-29.el7_8.2.src as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-0:4.2.6p5-29.el7_8.2.src as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-0:4.2.6p5-29.el7_8.2.src as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-0:4.2.6p5-29.el7_8.2.src as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-doc-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-doc-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-doc-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-doc-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-perl-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-perl-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-perl-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntp-perl-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntpdate-0:4.2.6p5-29.el7_8.2.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntpdate-0:4.2.6p5-29.el7_8.2.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntpdate-0:4.2.6p5-29.el7_8.2.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntpdate-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntpdate-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntpdate-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedntpdate-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedsntp-0:4.2.6p5-29.el7_8.2.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedsntp-0:4.2.6p5-29.el7_8.2.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedsntp-0:4.2.6p5-29.el7_8.2.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedsntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedsntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedsntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • Fixedsntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

    https://access.redhat.com/errata/RHSA-2020:2663
  • FixedSIMA² Master Stationauma_psirt

    Upgrade your SIMA2 to software version 2.6 or above. The NTP service of the SIMA2 Master Station with software version V2.6 and above includes a current, supported version of ntpd.

  • FixedAFF660/665cisa_csaf_ot

    Update to upcoming AFF660/665 FW 04.6.01 release when available.

  • MitigationSIMA² Master Stationauma_psirt

    1. If your SIMA2 does not need to provide time information to other systems or synchronize itself with an NTP server, disable the NTP client on those systems. Please note that the NTP client is disabled by default in SIMA2 2. In case you must use the NTP server on an SIMA2, choose from the following options to reduce NTP-based risks: - Allow NTP traffic to/from trusted NTP clients only - Monitor the network for malicious NTP traffic going to/coming from the SIMA2 - Filter malicious NTP traffic going to/coming from the SIMA2 Monitor NTP server operations on your SIMA2 (server availability, correctness of advertised time, NTP-related log entries, etc.) 3. In case you must use the NTP client on an SIMA2, choose from the following options to reduce NTP-based risks: - Use trusted NTP servers only - Allow NTP traffic to/from trusted NTP servers only - Monitor the network for malicious NTP traffic targeting the SIMA2 - Filter malicious NTP traffic targeting the SIMA2 - Monitor NTP client operations on your SIMA2 (correctness of system time, NTP-related log entries, etc.)

  • MitigationAFF660/665cisa_csaf_ot

    Configure only trusted DNS server(s).

  • Workaroundntp-0:4.2.6p5-29.el7_8.2.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-0:4.2.6p5-29.el7_8.2.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-0:4.2.6p5-29.el7_8.2.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-0:4.2.6p5-29.el7_8.2.src as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-0:4.2.6p5-29.el7_8.2.src as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-0:4.2.6p5-29.el7_8.2.src as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-0:4.2.6p5-29.el7_8.2.src as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-debuginfo-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-doc-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-doc-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-doc-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-doc-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-perl-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-perl-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-perl-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntp-perl-0:4.2.6p5-29.el7_8.2.noarch as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntpdate-0:4.2.6p5-29.el7_8.2.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntpdate-0:4.2.6p5-29.el7_8.2.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntpdate-0:4.2.6p5-29.el7_8.2.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntpdate-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntpdate-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntpdate-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundntpdate-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundsntp-0:4.2.6p5-29.el7_8.2.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundsntp-0:4.2.6p5-29.el7_8.2.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundsntp-0:4.2.6p5-29.el7_8.2.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundsntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundsntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundsntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

  • Workaroundsntp-0:4.2.6p5-29.el7_8.2.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

02

cvss

Technical severity, 0–10. One row per scoring source.

7.4
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 5.8–7.4

v2.05.8mediumAV:N/AC:M/Au:N/C:N/I:P/A:Pprimary · NVD / NIST USexploitability 8.6 · impact 4.9
v3.17.4highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Hprimary · NVD / NIST USexploitability 2.2 · impact 5.2
v3.05.9mediumCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · cve@mitre.org USexploitability 2.2 · impact 3.6
v3.07.4highCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Hsecondary · CISA US
v3.16.8mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H/E:Usecondary · CVSS-BT (t0sche)
v3.17.4highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Hsecondary · AUMA PSIRT
v3.17.4highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Hsecondary · Red Hat Product Security US
v3.15.9mediumAV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · FSTEC (BDU) RU
v3.17.4highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Hsecondary · ENISA EU
v3.17.4highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Hsecondaryexploitability 2.2 · impact 5.2
03

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
04

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-330USprimaryCWE-330USCWE-330USCWE-330USCWE-358US
05

affected products (104)

Products and version ranges known to be affected.

showing 20 of 104
06

advisories (4)

Vendor and ecosystem advisories describing this.

  • RHSA-2020:2663Red Hat Security Advisory: ntp security update2020-06-23csaf · redhat_csafUS

    An update for ntp is now available for Red Hat Enterprise Linux 7. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • VDE-2022-032AUMA: Multiple Vulnerabilities in Automation Runtime NTP Service2022-08-09csaf · auma_psirtDE

    The SIMA2 Master Station features an NTP service based on ntpd, a reference implementation of the Network Time Protocol (NTP). Affected SIMA2 Master Stations with software version < V2.6 include an outdated version of ntpd which is affected by a large number of vulnerabilities

  • WID-SEC-W-2023-1737Juniper Patchday Juli 2023Deutsch2023-07-12csaf · cert_bundDE

    Ein Angreifer aus dem angrenzenden Netzwerk oder ein entfernter anonymer oder lokaler Angreifer kann mehrere Schwachstellen in verschiedenen Juniper Produkten ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen und seine Privilegien zu erweitern.

  • ICSA-23-234-01Hitachi Energy AFF66x2023-08-22icsa · cisa_csaf_otUS

    Successful exploitation of these vulnerabilities could allow an attacker to compromise availability, integrity, and confidentiality of the targeted devices.

07

also known as (4)

Other names and identifiers for this entity.

08

sources

Which sources assert this record, and when.

cnnvdenisa_euvdfstec_bduauma_psirtcert_bundcisa_csaf_otredhat_csafNVDCVE.orgMITRE
published 2020-06-04modified 2026-06-17
10

references (39)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan