Everything Everywhere All at Once…in 2038
summary
Explains that the 2036–2038 rollovers are a systemic vulnerability rooted in the 32‑bit 2038 Unix time_t pattern, not just a single bug, and shows empirical scans: ~40% of publicly reporting NTP servers risk the NTP rollover 2036, 2.5M clients yielded ~39% running v3, a 123k-server probe found ~50k that will roll over, SNMP sampling (15M) exposed ~600k with architecture hints, lab tests broke fuel-tank gauges and smart TVs (127k sinkhole hits, ~6% confirmed to crash), and a reference stress-testing framework for CERTs/PSIRTs is prototype-ready.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:35NTP rollover risks
- 11:07Why 2038 is a systemic and not a simple bug
- 18:13Vulnerable devices examples
- 25:39Measuring 2038 risks
- 30:10Policy and procurement
- 35:16Actionable steps
- 36:40Q&A
related talks
12mWhy we’ll never see time travellers of the 80s in year 2038
44mCritical Zero Days Remotely Compromise the Most Popular Real-Time OS
39mNight of the living vulnerabilities
35mPatterns and Anti-Patterns in Embedded Development: What Security Incidents...
41mY2038 and Utmp/Wtmp on 64bit Systems
44mNight of the living vulnerabilities
23mConflicts in Vulnerability Management and Patching- 35mPatterns and Anti-Patterns in Embedded Development: What Security Incidents...