CVE-2025-54848
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 · uneditedA denial of service vulnerability exists in the Modbus TCP and Modbus RTU over TCP functionality of Socomec DIRIS Digiware M-70 1.6.9. A specially crafted series of network requests can lead to a denial of service. An attacker can send a sequence of unauthenticated packets to trigger this vulnerability.An attacker can trigger this denial-of-service condition by sending a sequence of Modbus TCP messages to port 502 using the Write Single Register function code (6). The attack sequence begins with a message to register 58112 with a value of 1000, indicating that a configuration change will follow. Next, a message is sent to register 29440 with a value corresponding to the new Modbus address to be configured. Finally, a message to register 57856 with a value of 161 commits the configuration change. After this configuration change, the device will be in a denial-of-service state.
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 · high confidenceA denial of service vulnerability in Socomec DIRIS Digiware M-70 version 1.6.9 allows unauthenticated attackers to permanently disable the device by sending three specific Modbus TCP Write Single Register (function code 6) messages: first to register 58112 with value 1000 to signal a configuration change, then to register 29440 with a new Modbus address, and finally to register 57856 with value 161 to commit the change, resulting in a non-responsive device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.6.9CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device firmware versionAccess the DIRIS Digiware M-70 web interface or use a Modbus read request to retrieve the firmware version information. This is typically found in the device information or system status page.Affected if The installed firmware version is exactly 1.6.9 - this is the only version listed as affected by this CVE.
-
Verify Modbus TCP service is accessibleScan the device network IP address for open TCP port 502 (Modbus TCP). Use a network scanner or the command 'nmap -p 502 <device_ip>' to confirm the service is listening.Affected if Port 502 is open and accessible from the network segment where the attacker would send the malicious packets.
-
Confirm device is currently responsiveAttempt to ping the device or send a Modbus TCP read request (such as function code 3 to read holding registers) to verify the device responds normally.Affected if The device does not respond to ping or Modbus queries, indicating it may have already been rendered non-responsive by the attack sequence.
-
Review Modbus traffic logsIf network monitoring or IDS/IPS is in place, review logs for patterns involving Write Single Register (function code 6) messages to registers 58112, 29440, and 57856, particularly with values 1000 and 161.Affected if Such suspicious Modbus traffic patterns are observed in network logs, suggesting the attack has been attempted or successfully executed.
A user is affected if the device runs firmware version 1.6.9, has Modbus TCP port 502 accessible from an untrusted network, and is either currently non-responsive or shows evidence of the specific three-step Modbus write sequence in network logs.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor firmware update when available; as an interim compensating control, implement network segmentation and access controls to restrict Modbus TCP (port 502) access to only authorized devices and personnel.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54848 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54848 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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