dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2024-1917

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Integer Overflow or Wraparound vulnerability in Mitsubishi Electric Corporation MELSEC-Q Series and MELSEC-L Series CPU modules allows a remote unauthenticated attacker to execute malicious code on a target product by sending a specially crafted packet.

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

An integer overflow vulnerability exists in the packet processing routine of Mitsubishi Electric MELSEC-Q Series and MELSEC-L Series CPU modules. A remote unauthenticated attacker can send a specially crafted packet that triggers the overflow, enabling execution of arbitrary malicious code on the target industrial controller.

MitigationIsolate affected CPU modules from untrusted networks using network segmentation and apply vendor-supplied patches when released; implement compensating controls such as firewall rules restricting access to PLC management interfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the CPU module model
    Access the PLC programming software (GX Works2 or GX Works3) and check the connected CPU module model designation. Look for model numbers containing 'Q' (MELSEC-Q Series) or 'L' (MELSEC-L Series) in the system configuration.
    Affected if The model is a Mitsubishi Electric MELSEC-Q Series or MELSEC-L Series CPU module.
  2. Determine the firmware version
    In GX Works3 or GX Works2, navigate to the CPU module diagnostics or system information section to retrieve the firmware version. Alternatively, check the nameplate sticker on the physical CPU module for the serial number and version label.
    Affected if The installed firmware version is earlier than the patched version released by Mitsubishi Electric for this CVE.
  3. Verify network exposure of PLC management interfaces
    Review network firewall rules and access control lists to determine if ports used by the MELSEC protocol (such as TCP/5007 for MELSOFT connections, UDP/5006 for MELSEC communications, and HTTP ports for web-based management) are accessible from external or untrusted network segments.
    Affected if The PLC management interfaces are reachable from untrusted or external networks without proper network segmentation.
  4. Check for anomalous packet traffic
    Capture network traffic on the PLC segment using a network tap or SPAN port. Analyze the captured packets for unusually large or malformed MELSEC protocol packets that could indicate exploitation attempts.
    Affected if Network logs or captures show malformed MELSEC packets that could trigger the integer overflow in packet processing.
  5. Inspect PLC program integrity
    Use the programming software to perform a program verification or compare the current program against a known-good backup. Check for unauthorized program changes that could indicate successful exploitation.
    Affected if The PLC program has been modified without authorized changes, or unexpected programs/modules are present in the CPU module.

A user is affected if they operate a MELSEC-Q or MELSEC-L Series CPU module with a vulnerable firmware version that is exposed to untrusted networks where an attacker could send specially crafted packets to trigger the integer overflow.

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

Isolate affected CPU modules from untrusted networks using network segmentation and apply vendor-supplied patches when released; implement compensating controls such as firewall rules restricting access to PLC management interfaces.

Have this fixed Scoped from the published advisory
  • Consultation12.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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