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

> An attacker can manipulate system time to trigger a denial of service, causing administrative lockout and operational failures in the tank gauge system.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2025
- **Updated:** 23 Oct 2025
- **Also known as:** GHSA-prwc-ww33-6c67

## What is CVE-2025-55067?

CVE-2025-55067 is a high-severity vulnerability in Veeder-Root TLS4B Automatic Tank Gauge System, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-55067?


## How do I fix CVE-2025-55067?

No fix has been published for CVE-2025-55067 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-55067 being exploited?

There is no known exploitation of CVE-2025-55067 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55067 and fix it if it is affected.

What it is: CVE-2025-55067 is a high-severity vulnerability in Veeder-Root TLS4B Automatic Tank Gauge System, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55067 in the wild and no public exploit code.

Affected product: Veeder-Root TLS4B Automatic Tank Gauge System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-55067/ (Markdown: https://insights.sbomify.com/CVE-2025-55067/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55067
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55067
- OSV: https://osv.dev/vulnerability/CVE-2025-55067

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-55067/
Summaries are generated and may contain mistakes; the official description above is the record.