CVE-2024-48882
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 functionality of Socomec DIRIS Digiware M-70 1.6.9. A specially crafted network packet can lead to denial of service. 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 confidenceA denial of service vulnerability exists in the Modbus TCP implementation of Socomec DIRIS Digiware M-70 version 1.6.9. An unauthenticated attacker on the network can send specially crafted Modbus TCP packets to cause the device to become unresponsive or crash, disrupting power monitoring operations.
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.
-
Verify device model is DIRIS Digiware M-70Access the device web interface, check the device information page, or query the device via Modbus to confirm the exact model name. Alternatively, check the physical device label or documentation.Affected if Device model is not Socomec DIRIS Digiware M-70 - not affected
-
Check firmware version 1.6.9Navigate to the device web interface System Info or Firmware section, or use the device management software to view the installed firmware version. The version is displayed as a numeric value (e.g., 1.6.9).Affected if Firmware version is exactly 1.6.9 - affected. If version differs (higher or lower), not affected based on provided data
-
Confirm Modbus TCP is enabledCheck the device configuration settings for Modbus TCP protocol. This is typically found in Communication settings or Protocol configuration in the web interface. Verify that Modbus TCP is listed as enabled and configured with a port number (default 502).Affected if Modbus TCP is disabled or not configured - not vulnerable as the attack vector requires active Modbus TCP service
-
Verify network accessibility of port 502From a network perspective, verify the device is reachable on TCP port 502 from any network segment. Use a port scanner (e.g., nmap -p 502 <device_ip>) or check if the device responds to Modbus TCP queries on port 502.Affected if Port 502 is accessible from untrusted network segments - vulnerable to remote attack. If port 502 is blocked or only accessible from isolated management network, risk is reduced
The environment is affected if the device is a Socomec DIRIS Digiware M-70 running firmware version 1.6.9 with Modbus TCP enabled and accessible on the network.
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 dataImplement network segmentation to isolate the DIRIS device on a restricted VLAN, configure firewall rules to limit Modbus TCP (port 502) access to authorized PLCs/SCADA systems only, and monitor for unusual Modbus traffic patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48882 — 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-2024-48882 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