Veeder-Root TLS4B CVE-2025-55067

Requires the ability to set or manipulate the TLS4B ATG system clock to a value at or beyond the January 19, 2038 32-bit Unix epoch boundary, which per the CVSS vector (PR:L) presumes authenticated low-privilege access to the device's time-configuration function over the network; no user interaction is needed (UI:N). The fault is deterministic - it also triggers spontaneously when the real-world clock reaches 2038 - so the practical limiting factor is reachability of and authentication to the time-setting interface rather than any special exploit condition. Impact is bounded to availability and minor integrity (log corruption); there is no confidentiality exposure and no scope change to other systems.

Signals are moderate and internally consistent rather than alarming. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) describes a network-reachable but low-privilege-authenticated attack with no user interaction, and the impact profile is availability-dominant (VA:H) with minor integrity loss (VI:L, corrupted logs) and no confidentiality impact (VC:N) - matching the stated DoS/administrative-lockout outcome. EPSS is low at 0.45% (37th percentile), there is no CISA KEV listing, and no public exploit was identified, so this is not an actively exploited or imminently wormable threat. The CWE-190 (integer overflow) / Y2038 nature means the core failure is time-triggered and deterministic: it will occur on its own at the January 19, 2038 rollover regardless of any attacker, while the 'attacker manipulates system time' path merely accelerates an inevitable fault and requires PR:L access to the device. Net assessment: a legitimate operational-reliability and OT-availability concern for fuel-dispensing environments, but a medium-priority patch item today rather than an emergency - the real-world urgency is driven by long-term operational continuity, not opportunistic mass exploitation. One caveat to verify: the description frames the trigger as the device reaching a specific date, so the network vector (AV:N) applies to the time-manipulation abuse path and presumes an attacker can reach and authenticate to the time-setting function - confirm the device's time configuration is not exposed unauthenticated.

A low-privileged but authenticated user (or an attacker who has obtained valid credentials) reaches the TLS4B ATG over the network and sets the system clock at or past the 2038 epoch boundary. The 32-bit Unix time value overflows and rolls back to December 13, 1901, breaking authentication, history visibility, and leak-detection termination, which locks administrators out and disrupts core tank-monitoring operations. No public exploit code is known; the same fault also triggers spontaneously when real time reaches January 19, 2038.