Categories
CVE-2025-55068 high CVSS 8.2

Vulnerability in Dover Fueling Solutions ProGauge MagLink LX4 Devices (CVE-2025-55068)

Summary

Vulnerability in Dover Fueling Solutions ProGauge MagLink LX4 Devices (CVE-2025-55068). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

Dover Fueling Solutions ProGauge MagLink LX4 Devices fail to handle Unix time values beyond a certain point.
An attacker can manually change the system time to exploit this
limitation, potentially causing errors in authentication and leading to a
denial-of-service condition.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-55068 has been found in Dover Fueling Solutions ProGauge MagLink LX4 Devices.
Risk of unauthorized operations or information disclosure. CVSS score: 8.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Dover Fueling Solutions ProGauge MagLink LX4 Devices CVE-2025-55068" on the vendor's site.

CVE-2025-55068 (Dover Fueling Solutions ProGauge MagLink LX4 Devices) — CWE-190 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-190) exists in Dover Fueling Solutions ProGauge MagLink LX4 Devices.

📍 Affected scope

Check the vendor advisory for the affected versions of Dover Fueling Solutions ProGauge MagLink LX4 Devices.

🔥 Severity

Severity: High (CVSS 8.2/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Dover Fueling Solutions ProGauge MagLink LX4 Devices を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details