CVE-2025-30519
📋 TL;DR
Dover Fueling Solutions ProGauge MagLink LX4 devices have hardcoded default root credentials that cannot be changed through normal administrative interfaces. This allows attackers with network access to gain full administrative control of the system. Organizations using these fuel management consoles are affected.
💻 Affected Systems
- Dover Fueling Solutions ProGauge MagLink LX4 Console
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Complete compromise of fuel management infrastructure allowing attackers to manipulate fuel levels, disable alarms, exfiltrate sensitive operational data, or use the device as a pivot point into other industrial control systems.
Likely Case
Unauthorized administrative access leading to configuration changes, data theft, or disruption of fuel monitoring operations.
If Mitigated
Limited impact if devices are properly segmented and access controls prevent unauthorized network access.
🎯 Exploit Status
Exploitation requires only network access and knowledge of default credentials; no special tools or skills needed.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Check with vendor for specific firmware version
Vendor Advisory: https://www.doverfuelingsolutions.com/mea/en/products-and-solutions/automatic-tank-gauging/consoles/progauge-maglink-lx-4-console.html
Restart Required: Yes
Instructions:
1. Contact Dover Fueling Solutions support for patched firmware. 2. Backup device configuration. 3. Apply firmware update following vendor instructions. 4. Verify credentials can be changed post-update.
🔧 Temporary Workarounds
Network Segmentation
allIsolate ProGauge devices on separate VLAN with strict firewall rules
Access Control Lists
allImplement IP-based access restrictions to limit which systems can communicate with the devices
🧯 If You Can't Patch
- Implement strict network segmentation to isolate devices from untrusted networks
- Deploy network monitoring and intrusion detection specifically for these devices
🔍 How to Verify
Check if Vulnerable:
Attempt to authenticate to the device using default root credentials via SSH or web interfaceCheck Version:
Check device web interface or console for firmware version informationVerify Fix Applied:
After patching, verify that default credentials no longer work and that new credentials can be set📡 Detection & Monitoring
Log Indicators:
- Multiple failed login attempts followed by successful root login
- Authentication from unexpected IP addresses
Network Indicators:
- SSH or administrative protocol traffic to ProGauge devices from unauthorized sources
SIEM Query:
source_ip="*" AND destination_ip="[ProGauge_IP]" AND (protocol="ssh" OR protocol="http") AND event_type="authentication_success"