A flaw was found in Clmg, where with the help of a maliciously crafted pandore or bmp file with modified dx and dy header field values it is possible to trick the application into allocating huge buffer sizes like 64 Gigabyte upon reading the file from disk or from a virtual buffer.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Cimg | Cimg | * | 3.1.0 (excluding) |
| Cimg | Ubuntu | bionic | * |
| Cimg | Ubuntu | esm-apps/bionic | * |
| Cimg | Ubuntu | esm-apps/focal | * |
| Cimg | Ubuntu | esm-apps/jammy | * |
| Cimg | Ubuntu | esm-apps/xenial | * |
| Cimg | Ubuntu | focal | * |
| Cimg | Ubuntu | jammy | * |
| Cimg | Ubuntu | kinetic | * |
| Cimg | Ubuntu | lunar | * |
| Cimg | Ubuntu | mantic | * |
| Cimg | Ubuntu | trusty | * |
| Cimg | Ubuntu | upstream | * |
| Cimg | Ubuntu | xenial | * |
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.