In kdeconnect-kde (aka KDE Connect) before 20.08.2, an attacker on the local network could send crafted packets that trigger use of large amounts of CPU, memory, or network connection slots, aka a Denial of Service attack.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Kdeconnect | Kde | * | 20.08.2 (excluding) |
| Kdeconnect | Ubuntu | bionic | * |
| Kdeconnect | Ubuntu | devel | * |
| Kdeconnect | Ubuntu | esm-apps/bionic | * |
| Kdeconnect | Ubuntu | esm-apps/focal | * |
| Kdeconnect | Ubuntu | esm-apps/jammy | * |
| Kdeconnect | Ubuntu | esm-apps/noble | * |
| Kdeconnect | Ubuntu | esm-apps/xenial | * |
| Kdeconnect | Ubuntu | focal | * |
| Kdeconnect | Ubuntu | groovy | * |
| Kdeconnect | Ubuntu | hirsute | * |
| Kdeconnect | Ubuntu | impish | * |
| Kdeconnect | Ubuntu | jammy | * |
| Kdeconnect | Ubuntu | kinetic | * |
| Kdeconnect | Ubuntu | lunar | * |
| Kdeconnect | Ubuntu | mantic | * |
| Kdeconnect | Ubuntu | noble | * |
| Kdeconnect | Ubuntu | oracular | * |
| Kdeconnect | Ubuntu | plucky | * |
| Kdeconnect | Ubuntu | trusty | * |
| Kdeconnect | 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.