Skip to main content

Traceability loss - Server's clock

Description​

The systems internal clock is not synced with NTP servers.

Impact​

Write log entries with a wrong date.

Recommendation​

Sync the server date with a NTP server.

Threat​

Anonymous attacker from the Internet.

Expected Remediation Time​

⌚ 30 minutes.

Score​

Default score using CVSS 3.1. It may change depending on the context of the vulnerability.

Base​

  • Attack vector: N
  • Attack complexity: L
  • Privileges required: N
  • User interaction: N
  • Scope: U
  • Confidentiality: N
  • Integrity: L
  • Availability: N

Temporal​

  • Exploit code madurity: X
  • Remediation level: O
  • Report confidence: X

Result​

  • Vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:X/RL:O/RC:X
  • Score:
    • Base: 5.3
    • Temporal: 5.1
  • Severity:
    • Base: Medium
    • Temporal: Medium

Code Examples​

Compliant code​

The clock is correctly configured for all the server responses

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Server: Werkzeug/2.0.1 Python/3.8.9
Date: Tue, 01 Feb 2022 20:38:00 GMT

Non compliant code​

The http headers shown an incorrectly set up clock

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Server: Werkzeug/2.0.1 Python/3.8.9
Date: Tue, 01 Feb 2022 "Wrong Clock" GMT

Requirements​

free trial

Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.