TCP Timestamps Enabled
The host includes TCP timestamps in its traffic, which on some systems lets an observer estimate how long it has been running since it was last restarted.
| Severity | Informational |
| CVSS 3.1 | 0 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.0 | 0 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 |
| CWE | CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere |
| OWASP Top 10 | A01:2025 Broken Access Control |
| MITRE ATT&CK | T1592 Gather Victim Host Information |
| Category | Information Disclosure |
Description
The TCP timestamp option, defined in RFC 7323 (which replaced RFC 1323), adds timestamp values to TCP segments so that hosts can measure round-trip times and reject old duplicate segments on fast connections. It is enabled by default on many operating systems, including Linux, and is a normal part of TCP.
On systems where the timestamp counter starts from a fixed value at boot and increases at a steady rate, sampling it over a short period lets an observer calculate the system's uptime. An uptime estimate can indicate that a host has not been restarted for a long time and may therefore lack updates that need a restart. Timestamps can also help to tell apart several hosts behind a load balancer or address translation device, since each keeps its own counter, so counting distinct timestamp sequences can reveal how many servers sit behind one address. The disclosure is minor: neither gives access to the host or affects its data, and the option itself benefits TCP performance.
Current Linux kernels add a secret random offset to the values they send, which prevents uptime being inferred, although scanners still report that the option is supported. The option is identified from a host's responses, for example by Nmap's operating system detection, which reports an uptime guess when the values allow one, or with the --tcp-timestamp option of hping3.
Remediation
For most hosts this finding can be accepted, as the option supports TCP performance and current operating systems already resist uptime inference. Where the organisation wishes to act on it:
- On Linux, keep the default
net.ipv4.tcp_timestamps = 1, which uses random offsets, rather than2, which does not. Setting0disables timestamps entirely, but can reduce performance on high-speed links. - On Windows, timestamps can be turned off with
netsh interface tcp set global timestamps=disabled. - On load balancers and firewalls that proxy or normalise TCP connections, use any available option to remove or rewrite TCP timestamps, so that the servers behind them cannot be told apart.
- Keep systems patched and restart them when updates require it, so that uptime reveals little of value.
Confirm any change by repeating the scan and checking whether the timestamp option is still returned and whether an uptime estimate is still available.
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 trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.