First published: Fri Nov 20 2020(Updated: )
Uncontrolled resource consumption vulnerability in MELSEC iQ-R Series modules (R00/01/02CPU firmware version '19' and earlier, R04/08/16/32/120 (EN) CPU firmware version '51' and earlier, R08/16/32/120SFCPU firmware version '22' and earlier, R08/16/32/120PCPU firmware version '25' and earlier, R08/16/32/120PSFCPU firmware version '06' and earlier, RJ71EN71 firmware version '47' and earlier, RJ71GF11-T2 firmware version '47' and earlier, RJ72GF15-T2 firmware version '07' and earlier, RJ71GP21-SX firmware version '47' and earlier, RJ71GP21S-SX firmware version '47' and earlier, and RJ71GN11-T2 firmware version '11' and earlier) allows a remote unauthenticated attacker to cause an error in a CPU unit and cause a denial-of-service (DoS) condition in execution of the program and its communication, or to cause a denial-of-service (DoS) condition in communication via the unit by receiving a specially crafted SLMP packet
Credit: vultures@jpcert.or.jp
Affected Software | Affected Version | How to fix |
---|---|---|
Mitsubishielectric R00cpu Firmware | <=19 | |
Mitsubishielectric R00cpu | ||
Mitsubishielectric R01cpu Firmware | <=19 | |
Mitsubishielectric R01cpu | ||
Mitsubishielectric R02cpu Firmware | <=19 | |
Mitsubishielectric R02cpu | ||
Mitsubishielectric R04cpu Firmware | <=51 | |
Mitsubishielectric R04cpu | ||
Mitsubishielectric R08cpu Firmware | <=51 | |
Mitsubishielectric R08cpu | ||
Mitsubishielectric R16cpu Firmware | <=51 | |
Mitsubishielectric R16cpu | ||
Mitsubishielectric R32cpu Firmware | <=51 | |
Mitsubishielectric R32cpu | ||
Mitsubishielectric R120cpu Firmware | <=51 | |
Mitsubishielectric R120cpu | ||
Mitsubishielectric R08sfcpu Firmware | <=22 | |
Mitsubishielectric R08sfcpu | ||
Mitsubishielectric R16sfcpu Firmware | <=22 | |
Mitsubishielectric R16sfcpu | ||
Mitsubishielectric R32sfcpu Firmware | <=22 | |
Mitsubishielectric R32sfcpu | ||
Mitsubishielectric R120sfcpu Firmware | <=22 | |
Mitsubishielectric R120sfcpu | ||
Mitsubishielectric R08pcpu Firmware | <=25 | |
Mitsubishielectric R08pcpu | ||
Mitsubishielectric R16pcpu Firmware | <=25 | |
Mitsubishielectric R16pcpu | ||
Mitsubishielectric R32pcpu Firmware | <=25 | |
Mitsubishielectric R32pcpu | ||
Mitsubishielectric R120pcpu Firmware | <=25 | |
Mitsubishielectric R120pcpu | ||
Mitsubishielectric R08psfcpu Firmware | <=06 | |
Mitsubishielectric R08psfcpu | ||
Mitsubishielectric R16psfcpu Firmware | <=06 | |
Mitsubishielectric R16psfcpu | ||
Mitsubishielectric R32psfcpu Firmware | <=06 | |
Mitsubishielectric R32psfcpu | ||
Mitsubishielectric R120psfcpu Firmware | <=06 | |
Mitsubishielectric R120psfcpu | ||
Mitsubishielectric Rj71en71 Firmware | <=47 | |
Mitsubishielectric Rj71en71 | ||
Mitsubishielectric Rj71gf11-t2 Firmware | <=47 | |
Mitsubishielectric Rj71gf11-t2 | ||
Mitsubishielectric Rj72gf15-t2 Firmware | <=07 | |
Mitsubishielectric Rj72gf15-t2 | ||
Mitsubishielectric Rj71gp21-sx Firmware | <=47 | |
Mitsubishielectric Rj71gp21-sx | ||
Mitsubishielectric Rj71gp21s-sx Firmware | <=47 | |
Mitsubishielectric Rj71gp21s-sx | ||
Mitsubishielectric Rj71c24-r2 Firmware | <=47 | |
Mitsubishielectric Rj71c24-r2 | ||
Mitsubishielectric Rj71c24-r4 Firmware | <=47 | |
Mitsubishielectric Rj71c24-r4 | ||
Mitsubishielectric Rj71gn11-t2 Firmware | <=11 | |
Mitsubishi Electric RJ71GN11-T2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-5668 has a high severity rating due to the potential for uncontrolled resource consumption, which can lead to a denial of service.
To fix CVE-2020-5668, update your MELSEC iQ-R Series modules to the latest firmware version as recommended by Mitsubishi Electric.
CVE-2020-5668 affects R00/01/02CPU firmware versions '19' and earlier, R04/08/16/32/120 (EN) CPU firmware versions '51' and earlier, and several other specific firmware versions.
Yes, CVE-2020-5668 can lead to significant system downtime due to resource exhaustion if exploited.
Currently, the best approach for CVE-2020-5668 is to upgrade to the patched firmware, as there are no cited workarounds for the vulnerability.