Mammoth2025h1 log entry 1021714 later timestamp than next STH

[Luke Valenta]

Hi folks,

We noticed an entry in the mammoth2025h1 log which had a timestamp ahead of the bounding tree head. We only picked this up since we happened to poll the latest STH at exactly the right time to catch the discrepancy. We reported to the Sectigo team earlier this week and they're starting an investigation.

Mammoth2025h1’s entry 1021714 has timestamp 1717928700088 (2024-06-09 10:25:00.088 GMT), but we recorded a STH with tree_size 1021715 above it with timestamp 1717928699927 (2024-06-09 10:24:59.927 GMT) [1], 161 milliseconds prior to the entry’s timestamp.

[1]
{"tree_size":1021715,"timestamp":1717928699927,"sha256_root_hash":"Wa3eDh/g7KyE4CdzEJzw6RglnFGwBQH54OUupZTRb7M=","tree_head_signature":"BAMARzBFAiEAjg+6uNUUSfmbg9nQDc5XX4J36EJfzF4nUdm0dDxHBx4CIFTUCEt+atRig9pOSy40\nq8hWUj5u1ppwnZG+gnIOPxE1"}

Best,
Luke

--

Luke Valenta

Systems Engineer - Research