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
The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| R00cpu_firmware | Mitsubishielectric | * | 19 (including) |
Limited resources include memory, file system storage, database connection pool entries, and CPU. If an attacker can trigger the allocation of these limited resources, but the number or size of the resources is not controlled, then the attacker could cause a denial of service that consumes all available resources. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system. There are at least three distinct scenarios which can commonly lead to resource exhaustion:
Resource exhaustion problems are often result due to an incorrect implementation of the following situations:
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.