MEDIUM: NTP Version Report

DESCRIPTION LAST UPDATED: 2023-12-18

DEFAULT SEVERITY LEVEL: MEDIUM

This report identifies NTP servers that have the potential to be used in amplification attacks by criminals that wish to perform denial of service attacks.

The NTP version command is a Mode 6 query for READVAR. While not as bad as the Mode 7 query for MONLIST, the queries for READVAR will normally provide around 30x amplification.

To manually test if a system is vulnerable to this, you can use the command:

ntpq -c rv [ip]
  • Instructions for restricting READVAR for linux hosts can be found here.
  • Instructions for restricting READVAR for Cisco gear can be found here.

You can track latest NTP version exposure on our Dashboard.

You can learn more on the report in our NTP Version Report tutorial.

You can learn more on our reports in general in our Overview of Free Public Benefit Shadowserver Reports presentation, which also explains example Use Cases.

Severity levels are described here.

For more information on our scanning efforts, check out our Internet scanning summary page..

This report has an IPv4 and IPv6 version.

Filename(s): scan_ntp, scan6_ntp

 

Fields

  • timestamp
    Time that the IP was probed in UTC+0
  • severity
    Severity level
  • ip
    The IP address of the device in question
  • protocol
    Protocol that the NTP response came on (UDP)
  • port
    Port that the NTP response came from
  • hostname
    Reverse DNS name of the device in question
  • tag
    Set to ntpversion
  • asn
    ASN of where the device in question resides
  • geo
    Country where the device in question resides
  • region
    State / Province / Administrative region where the device in question resides
  • city
    City in which the device in question resides
  • version
    NTP software version and build time
  • clk_wander
    Clock frequency wander (PPM)
  • clock
    Date and time of day
  • error
    Frequency error
  • frequency
    Frequency offset (PPM) relative to hardware clock
  • jitter
    Clock jitter
  • leap
    Leap warning indicator (0-3)
  • mintc
    Minimum time constant (log2 s) (3-10)
  • noise
    "White phase" noise, aka jitter
  • offset
    Combined offset of server relative to this host
  • peer
    An identification number of the peer in use
  • phase
    Combined offset of server relative to this host
  • poll
    Poll messages sent (for association with a reference clock)
  • precision
    Precision (log2 s)
  • processor
    Hardware platform and version
  • refid
    Reference ID or kiss code
  • reftime
    Reference time
  • rootdelay
    Total roundtrip delay to the primary reference clock
  • rootdispersion
    Total dispersion to the primary reference clock
  • stability
    PPM mean frequency deviation
  • state
    The current mode of NTP operation, where 1 is symmetric active, 2 is symmetric passive, 3 is client, 4 is server, and 5 is broadcast
  • stratum
    The stratum of the peer server (1-15) — anything greater than 1 is a secondary reference
  • system
    Operating system and version
  • tai
    TAI-UTC offest (s)
  • tc
    Time constant and poll exponent (log2 s) (3-17)
  • naics
    North American Industry Classification System Code
  • hostname_source
    Hostname source
  • sector
    Sector the IP belongs to
  • response_size
    Response size in bytes
  • amplification
    Amplification factor (This amplification is is based solely on the payload size sent and payload size received)

Sample

"timestamp","severity","ip","protocol","port","hostname","tag","asn","geo","region","city","version","clk_wander","clock","error","frequency","jitter","leap","mintc","noise","offset","peer","phase","poll","precision","processor","refid","reftime","rootdelay","rootdispersion","stability","state","stratum","system","tai","tc","naics","hostname_source","sector","response_size","amplification"
"2010-02-10 00:00:00",medium,192.168.0.1,udp,123,node01.example.com,ntpversion,64512,ZZ,Region,City,4,,0xE90BEC89.7993E17A,,,,0,3,,,44565,,,-22,unknown,198.19.255.251,0xE90BD488.734331E3,,,,,4,UNIX,,10,0,,,288,24.00
"2010-02-10 00:00:01",medium,192.168.0.2,udp,123,node02.example.com,ntpversion,64512,ZZ,Region,City,4,,0xE90BEC89.EA212E4A,,10.707,0.02,0,,0.087,-0.125,61438,,9,-24,unknown,57.7.41.198,0xE90BE61B.4915CB5E,259.229,83.179,0.001,4,4,UNIX,,,0,,"Communications, Service Provider, and Hosting Service",324,27.00
"2010-02-10 00:00:02",medium,192.168.0.3,udp,123,node03.example.com,ntpversion,64512,ZZ,Region,City,4,0.008,0xE90BEC89.EBC6AA78,,8.536,27.709,0,3,,12.599,62647,,,-10,unknown,192.168.244.1,0xE90BC8D6.5A1CAD00,8.584,165.843,,,3,UNIX,,10,0,,,328,27.33

Our 132 Report Types

« Back to Network Reporting