HawkScan Test Info for Timestamp Disclosure - Unix

Timestamp Disclosure - Unix


Plugin Id: 10096 | CWE: 200


To remediate the vulnerability of timestamp disclosure in Unix, the following steps can be taken:

  1. Disable timestamp disclosure: Modify the Unix server configuration to prevent the disclosure of timestamps by the application or web server. This can typically be achieved by adjusting the server’s logging settings or by disabling the specific feature that is causing the disclosure.

    Example for Apache HTTP Server:

    # Disable timestamp disclosure in Apache access logs
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    CustomLog /var/log/apache2/access.log common
  2. Regularly update and patch the server: Keep the Unix server up to date with the latest security patches and updates. This helps to address any known vulnerabilities, including those related to timestamp disclosure.

  3. Implement access controls: Ensure that appropriate access controls are in place to restrict access to sensitive information, including timestamps. This can involve configuring file permissions, user privileges, and network security measures.


The vulnerability of timestamp disclosure in Unix occurs when an application or web server inadvertently reveals the timestamp of a request or response. This can happen through various means, such as including the timestamp in server logs or error messages. The disclosure of timestamps can provide attackers with valuable information about the system’s activity and potentially aid in further attacks.


The risks associated with timestamp disclosure in Unix include:

  • Information leakage: Attackers can gain insights into the system’s activity patterns, which may reveal sensitive information or assist in identifying potential vulnerabilities.

  • Attack surface expansion: Timestamp disclosure can provide attackers with additional information that can be used to launch more targeted attacks against the system or its users.

  • Privacy concerns: The disclosure of timestamps may violate privacy regulations or policies, especially if the timestamps are associated with personally identifiable information (PII) or sensitive data.

  • Reconnaissance for timing-based attacks: Attackers can use the disclosed timestamps to gather information for timing-based attacks, such as timing attacks or replay attacks, which rely on precise timing measurements.