Mitsubishi Electric MELSEC-Q Series PLCs Resource Exhaustion
Mitsubishi Electric Q03/04/06/13/26UDVCPU: serial number 20081 and prior, Q04/06/13/26UDPVCPU: serial number 20081 and prior, and Q03UDECPU, Q04/06/10/13/20/26/50/100UDEHCPU: serial number 20101 and prior. A remote attacker can send specific bytes over Port 5007 that will result in an Ethernet stack crash and disruption to USB communication.
- Published
- Feb 5, 2019
- Updated
- Jun 16, 2026
- EPSS
- 4.3% · 91th percentile
- CWE
- CWE-400
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.3%
CNA vs NVD score
- NVD
- 7.5
- CNA · icscert
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| mitsubishielectric | q03udvcpu firmware | cpe:2.3:o:mitsubishielectric:q03udvcpu_firmware |
| mitsubishielectric | q03udvcpu | cpe:2.3:h:mitsubishielectric:q03udvcpu |
| mitsubishielectric | q04udvcpu firmware | cpe:2.3:o:mitsubishielectric:q04udvcpu_firmware |
| mitsubishielectric | q04udvcpu | cpe:2.3:h:mitsubishielectric:q04udvcpu |
| mitsubishielectric | q06udvcpu firmware | cpe:2.3:o:mitsubishielectric:q06udvcpu_firmware |
| mitsubishielectric | q06udvcpu | cpe:2.3:h:mitsubishielectric:q06udvcpu |
| mitsubishielectric | q13udvcpu firmware | cpe:2.3:o:mitsubishielectric:q13udvcpu_firmware |
| mitsubishielectric | q13udvcpu | cpe:2.3:h:mitsubishielectric:q13udvcpu |
| mitsubishielectric | q26udvcpu firmware | cpe:2.3:o:mitsubishielectric:q26udvcpu_firmware |
| mitsubishielectric | q26udvcpu | cpe:2.3:h:mitsubishielectric:q26udvcpu |
| mitsubishielectric | q04udpvcpu firmware | cpe:2.3:o:mitsubishielectric:q04udpvcpu_firmware |
| mitsubishielectric | q04udpvcpu | cpe:2.3:h:mitsubishielectric:q04udpvcpu |
and 24 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mitsubishielectric q03udecpu firmwareup to 20101 inclusive
- mitsubishielectric q03udvcpu firmwareup to 20081 inclusive
- mitsubishielectric q04udehcpu firmwareup to 20101 inclusive
- mitsubishielectric q04udpvcpu firmwareup to 20081 inclusive
- mitsubishielectric q04udvcpu firmwareup to 20081 inclusive
- mitsubishielectric q06udehcpu firmwareup to 20101 inclusive
- mitsubishielectric q06udpvcpu firmwareup to 20081 inclusive
- mitsubishielectric q06udvcpu firmwareup to 20081 inclusive
- mitsubishielectric q100udehcpu firmwareup to 20101 inclusive
- mitsubishielectric q10udehcpu firmwareup to 20101 inclusive
- mitsubishielectric q13udehcpu firmwareup to 20101 inclusive
- mitsubishielectric q13udpvcpu firmwareup to 20081 inclusive
- mitsubishielectric q13udvcpu firmwareup to 20081 inclusive
- mitsubishielectric q20udehcpu firmwareup to 20101 inclusive
- mitsubishielectric q26udehcpu firmwareup to 20101 inclusive
- mitsubishielectric q26udpvcpu firmwareup to 20081 inclusive
- mitsubishielectric q26udvcpu firmwareup to 20081 inclusive
- mitsubishielectric q50udehcpu firmwareup to 20101 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.
Mitsubishi Electric Q03/04/06/13/26UDVCPU
- up to and including serial number 20081affected
Mitsubishi Electric Q03UDECPU, Q04/06/10/13/20/26/50/100UDEHCPU
- up to and including serial number 20101affected
Mitsubishi Electric Q04/06/13/26UDPVCPU
- up to and including serial number 20081affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www.securityfocus.com/bid/106771
- www.cisa.gov/news-events/ics-advisories/icsa-19-029-02
- ics-cert.us-cert.gov/advisories/ICSA-19-029-02
Vendor advisories and official records. Exploit/PoC links are deliberately left out.