A vulnerability was found in JWCrypto. This flaw allows an attacker to cause a denial of service (DoS) attack and possible password brute-force and dictionary attacks to be more resource-intensive. This issue can result in a large amount of computational consumption, causing 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 |
|---|---|---|---|
| Jwcrypto | Latchset | * | 1.5.1 (excluding) |
| Red Hat Enterprise Linux 8 | RedHat | idm:client-8100020240417004735.143e9e98 | * |
| Red Hat Enterprise Linux 8 | RedHat | idm:DL1-8100020240416171943.823393f5 | * |
| Red Hat Enterprise Linux 9 | RedHat | python-jwcrypto-0:1.5.6-2.el9 | * |
| Python-jwcrypto | Ubuntu | bionic | * |
| Python-jwcrypto | Ubuntu | devel | * |
| Python-jwcrypto | Ubuntu | esm-apps/noble | * |
| Python-jwcrypto | Ubuntu | focal | * |
| Python-jwcrypto | Ubuntu | mantic | * |
| Python-jwcrypto | Ubuntu | noble | * |
| Python-jwcrypto | Ubuntu | oracular | * |
| Python-jwcrypto | Ubuntu | plucky | * |
| Python-jwcrypto | 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.