OpenKMIP PyKMIP version All versions before 0.8.0 contains a CWE 399: Resource Management Errors (similar issue to CVE-2015-5262) vulnerability in PyKMIP server that can result in DOS: the server can be made unavailable by one or more clients opening all of the available sockets. This attack appear to be exploitable via A client or clients open sockets with the server and then never close them. This vulnerability appears to have been fixed in 0.8.0.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Pykmip | Pykmip_project | * | 0.8.0 (excluding) |
| Python-pykmip | Ubuntu | bionic | * |
| Python-pykmip | Ubuntu | cosmic | * |
| Python-pykmip | Ubuntu | disco | * |
| Python-pykmip | Ubuntu | eoan | * |
| Python-pykmip | Ubuntu | focal | * |
| Python-pykmip | Ubuntu | groovy | * |
| Python-pykmip | Ubuntu | hirsute | * |
| Python-pykmip | Ubuntu | impish | * |
| Python-pykmip | Ubuntu | kinetic | * |
| Python-pykmip | Ubuntu | lunar | * |
| Python-pykmip | Ubuntu | mantic | * |
| Python-pykmip | Ubuntu | oracular | * |
| Python-pykmip | 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.