dbcve.org
Diris M 70 FirmwareOperating system · Socomec

CVE-2024-49572

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
A denial of service vulnerability exists in the Modbus TCP functionality of Socomec DIRIS Digiware M-70 1.6.9. A specially crafted network packet can lead to denial of service and weaken credentials resulting in default documented credentials being applied to the device. An attacker can send an unauthenticated packet to trigger this vulnerability.

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

A denial of service vulnerability exists in the Modbus TCP implementation of the Socomec DIRIS Digiware M-70 power monitoring device version 1.6.9. An unauthenticated attacker can send specially crafted network packets to trigger the vulnerability, causing denial of service and forcing the device to fall back to default documented credentials, effectively weakening access controls.

MitigationApply vendor-supplied firmware updates when available; implement network segmentation to restrict access to the Modbus TCP service to authorized systems only; change default credentials immediately if the device has reverted to them.

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
Diris M 70 FirmwareOperating system
Affected:= 1.6.9

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
Low
Integrity
Low
Availability
None

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

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. Confirm device model and firmware version
    Access the device's web interface or use Modbus/SNMP queries to retrieve the exact firmware version. For web interface, navigate to System > Information or similar status page. The device model should show DIRIS Digiware M-70.
    Affected if The device is a Socomec DIRIS Digiware M-70 running firmware version 1.6.9 exactly.
  2. Verify Modbus TCP service status
    Check if the Modbus TCP service is enabled and listening on the device. This can be done by scanning the device's IP on port 502 (default Modbus TCP port) using tools like nmap or netcat, or by checking the device configuration through its web interface under Network or Communication settings.
    Affected if Modbus TCP is enabled and accessible on the network.
  3. Assess network exposure of Modbus TCP
    Determine if the Modbus TCP port (502/TCP) is exposed to untrusted networks. Review firewall rules, VLAN segmentation, and network access control lists. Use network scanning to confirm whether the device is reachable from outside the management network.
    Affected if The Modbus TCP service is reachable from untrusted or outside networks without proper access controls.
  4. Check for credential fallback condition
    After a DoS condition occurs, the device may revert to default documented credentials. Attempt to authenticate to the device using the documented default credentials (consult product manual for factory defaults). If authentication succeeds with default credentials when custom credentials were previously set, the device has fallen back.
    Affected if The device accepts default documented credentials, indicating a fallback has occurred after a DoS event.

A user is affected if they have a DIRIS Digiware M-70 on firmware 1.6.9 with Modbus TCP enabled and accessible, where the device may have fallen back to default credentials following a denial of service attack.

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

Apply vendor-supplied firmware updates when available; implement network segmentation to restrict access to the Modbus TCP service to authorized systems only; change default credentials immediately if the device has reverted to them.

Fix this in Diris M 70 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49572 — 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-2024-49572 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