CVE-2019-6535: Mitsubishi Electric MELSEC-Q Series PLCs Resource Exhaustion
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.2% (FIRST EPSS); higher than 91.2% of all records.
- 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.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.2% · 91th percentile
- CWE
- CWE-400
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.2%
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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| 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
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
Affected versions · NVD (18)
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
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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
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.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.