A Denial of Service (DoS) condition is possible in OpenStack Mistral in versions up to and including 7.0.3. Submitting a specially crafted workflow definition YAML file containing nested anchors can lead to resource exhaustion culminating in a denial of service.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Openstack-mistral | Redhat | * | 7.0.3 (including) |
| Mistral | Ubuntu | bionic | * |
| Mistral | Ubuntu | eoan | * |
| Mistral | Ubuntu | esm-apps/bionic | * |
| Mistral | Ubuntu | groovy | * |
| Mistral | Ubuntu | hirsute | * |
| Mistral | Ubuntu | impish | * |
| Mistral | Ubuntu | kinetic | * |
| Mistral | Ubuntu | lunar | * |
| Mistral | Ubuntu | mantic | * |
| Mistral | Ubuntu | trusty | * |
| Mistral | Ubuntu | upstream | * |
| Mistral | 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.