ICMP Timestamp Response

The host answers ICMP timestamp requests, revealing the time on its system clock to any host that asks.

SeverityInformational
CVSS 3.10 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N Open in the calculator
CVSS 4.00 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere
OWASP Top 10A01:2025 Broken Access Control
MITRE ATT&CKT1124 System Time Discovery
CVECVE-1999-0524
CategoryInformation Disclosure

Description

ICMP timestamp requests (type 13) and replies (type 14), defined in RFC 792, let one host ask another for its current time, given in milliseconds since midnight Universal Time. Clock synchronisation now relies on NTP, so few systems need this facility, but many operating systems and network devices still answer timestamp requests unless a firewall drops them.

A reply discloses the host's clock to within milliseconds, which has little value on its own. In uncommon cases it can assist attacks on mechanisms that depend on the clock, such as random number generators seeded with the time or time-based authentication tokens. A reply also confirms that the host is live, which can matter where other probes are filtered or blocked. The behaviour does not affect the confidentiality, integrity or availability of the host or its data.

It is identified with Nmap's timestamp ping (-PP) or a tool such as hping3 (--icmp-ts), and vulnerability scanners report it as ICMP timestamp request remote date disclosure, usually with the reference CVE-1999-0524, a long-standing entry that also covers ICMP address mask replies.

Remediation

Drop ICMP timestamp requests at the network perimeter and on host firewalls, unless a specific application needs them:

  • On perimeter firewalls and routers, block inbound ICMP type 13 (timestamp request) and outbound type 14 (timestamp reply), while still allowing the ICMP types that networks need to work, such as destination unreachable, including its fragmentation needed message, and time exceeded.
  • On Linux hosts, drop the requests with iptables or nftables, as shown below.
  • On Cisco IOS devices, deny timestamp-request in the inbound interface access list.
  • Keep host clocks synchronised to a trusted time source, so that a disclosed time reveals nothing unexpected.
# iptables iptables -A INPUT -p icmp --icmp-type timestamp-request -j DROP iptables -A OUTPUT -p icmp --icmp-type timestamp-reply -j DROP # nftables (in an existing inet filter table with an input chain) nft add rule inet filter input icmp type timestamp-request drop # Cisco IOS extended access list entry deny icmp any any timestamp-request

Confirm the fix by sending a timestamp request again and checking that no reply is received.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Network Services Findings

Every Network Services finding