dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-2567

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An attacker could modify or disable settings, disrupt fuel monitoring and supply chain operations, leading to disabling of ATG monitoring. This would result in potential safety hazards in fuel storage and transportation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a critical vulnerability in Automatic Tank Gauging (ATG) systems used for fuel storage monitoring. An attacker can modify or disable settings within the ATG system, disrupting fuel monitoring and supply chain operations. The vulnerability allows attackers to disable ATG monitoring capabilities, creating potential safety hazards in fuel storage and transportation environments.

MitigationOrganizations should immediately isolate ATG systems on dedicated network segments with strict access controls, implement robust authentication for all configuration interfaces, and monitor for unauthorized configuration changes. Given the critical nature and safety implications, emergency assessment of affected ATG deployments is recommended.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ATG systems on the network
    Scan the network for devices running Automatic Tank Gauging protocols (common ports: 10001/TCP, 20000/TCP for Veeder-Root, or consult your specific ATG vendor documentation). Inventory all ATG console or controller IP addresses.
    Affected if ATG devices are found with routable network addresses accessible from untrusted segments.
  2. Verify network isolation of ATG management interfaces
    Review firewall rules and network segmentation to determine if ATG console/admin ports are accessible from non-production networks. Use 'netstat -an' on the ATG host or check switch ACLs to list accessible IPs.
    Affected if ATG management or configuration interfaces accept connections from networks outside the trusted OT/ICS segment.
  3. Confirm authentication is enforced on configuration interfaces
    Attempt to access the ATG web console or API endpoint without credentials (or with invalid credentials). Observe whether the system rejects the request or allows anonymous configuration changes.
    Affected if The ATG system allows configuration modifications (settings, alarms, disable commands) without requiring valid authentication.
  4. Check for unauthorized configuration changes in system logs
    Review ATG system event logs, audit logs, or console alerts for recent unexpected changes to tank parameters, alarm thresholds, or monitoring disable commands that were not initiated by authorized personnel.
    Affected if Recent configuration changes exist that were not performed by known administrators or correlate with authorized maintenance windows.
  5. Validate ATG monitoring status and connectivity
    Query the ATG system status (via console display, SNMP, or API) to confirm all tank sensors report online and fuel level/temperature monitoring is actively updating. Check for any tanks showing 'offline', 'disabled', or 'communication failure' status.
    Affected if Any tank monitoring entries show disabled status or communication failures not attributed to known maintenance.

A user is affected if their ATG system is network-accessible from untrusted segments AND allows unauthenticated configuration changes that can disable monitoring.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should immediately isolate ATG systems on dedicated network segments with strict access controls, implement robust authentication for all configuration interfaces, and monitor for unauthorized configuration changes. Given the critical nature and safety implications, emergency assessment of affected ATG deployments is recommended.

Have this fixed Scoped from the published advisory
  • Consultation16.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
60.0 hours of engineering $10,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $17,216.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2567 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data