Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-55067: CWE-190 Integer Overflow or Wraparound in Veeder-Root TLS4B Automatic Tank Gauge System

0
High
VulnerabilityCVE-2025-55067cvecve-2025-55067cwe-190
Published: Thu Oct 23 2025 (10/23/2025, 19:39:14 UTC)
Source: CVE Database V5
Vendor/Project: Veeder-Root
Product: TLS4B Automatic Tank Gauge System

Description

The TLS4B ATG system is vulnerable to improper handling of Unix time values that exceed the 2038 epoch rollover. When the system clock reaches January 19, 2038, it resets to December 13, 1901, causing authentication failures and disrupting core system functionalities such as login access, history visibility, and leak detection termination. This vulnerability could allow an attacker to manipulate the system time to trigger a denial of service (DoS) condition, leading to administrative lockout, operational timer failures, and corrupted log entries.

AI-Powered Analysis

AILast updated: 10/23/2025, 19:51:51 UTC

Technical Analysis

CVE-2025-55067 is an integer overflow vulnerability classified under CWE-190 affecting the Veeder-Root TLS4B Automatic Tank Gauge (ATG) system. The root cause is the improper handling of Unix time values that exceed the 32-bit signed integer limit, commonly known as the Year 2038 problem. When the system clock reaches the critical timestamp of January 19, 2038, the internal time counter wraps around, resetting the clock to December 13, 1901. This causes the TLS4B system to malfunction in several core areas: authentication mechanisms fail, preventing legitimate login access; historical data visibility is compromised, affecting audit and monitoring capabilities; and leak detection processes terminate unexpectedly, undermining environmental safety monitoring. An attacker can exploit this vulnerability remotely without requiring user interaction or elevated privileges by manipulating the system time or triggering the rollover condition, resulting in a denial of service (DoS). The DoS manifests as administrative lockout, operational timer failures, and corrupted log entries, which can severely disrupt fuel management operations and safety compliance. Although no known exploits are currently in the wild, the vulnerability's nature and timing make it a critical concern for organizations using the TLS4B system. The CVSS 4.0 base score of 7.1 reflects the high impact on availability and integrity, ease of exploitation, and lack of required user interaction. The vulnerability highlights the importance of addressing legacy time representation issues in embedded industrial control systems.

Potential Impact

For European organizations, the impact of CVE-2025-55067 is significant due to the critical role of the TLS4B ATG system in fuel storage and environmental safety monitoring. Disruption of authentication and operational functions can lead to administrative lockouts, preventing timely system management and incident response. Loss of historical data visibility impairs forensic investigations and compliance reporting, while termination of leak detection processes increases the risk of undetected fuel leaks, potentially causing environmental damage and regulatory penalties. The denial of service condition could halt fuel dispensing operations, affecting supply chains and industrial processes reliant on fuel availability. Given the reliance on automated tank gauges in fuel depots, transportation hubs, and industrial facilities across Europe, this vulnerability poses operational, safety, and compliance risks. The timing of the vulnerability coincides with the 2038 epoch rollover, necessitating proactive remediation to avoid widespread outages. Additionally, corrupted log entries reduce the ability to detect and respond to other security incidents, increasing overall cyber risk exposure.

Mitigation Recommendations

Mitigation of CVE-2025-55067 requires a multi-faceted approach: 1) Immediate engagement with Veeder-Root to obtain patches or firmware updates that address the 2038 time rollover issue is critical. If no patch is available, plan for system upgrades or replacements before the rollover date. 2) Implement strict network segmentation and access controls to limit exposure of TLS4B systems to untrusted networks, reducing the risk of remote exploitation. 3) Deploy time synchronization controls using secure and reliable NTP sources to prevent unauthorized or erroneous time changes that could trigger the vulnerability prematurely. 4) Monitor system logs and operational metrics for anomalies indicative of time manipulation or authentication failures. 5) Develop incident response plans specifically addressing potential DoS scenarios caused by this vulnerability, including manual override procedures for tank gauge operations. 6) Conduct regular audits of ATG system configurations and firmware versions to ensure compliance with security best practices. 7) Coordinate with environmental and safety teams to prepare for potential leak detection disruptions, ensuring alternative monitoring methods are in place. These targeted measures go beyond generic advice by focusing on the unique characteristics of the TLS4B system and the specific nature of the 2038 epoch rollover vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
icscert
Date Reserved
2025-09-23T19:56:48.001Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68fa85e2a3a2e7083d940cef

Added to database: 10/23/2025, 7:45:38 PM

Last enriched: 10/23/2025, 7:51:51 PM

Last updated: 10/23/2025, 11:03:01 PM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats