atop through 2.11.0 allows local users to cause a denial of service (e.g., assertion failure and application exit) or possibly have unspecified other impact by running certain types of unprivileged processes while a different user runs atop.
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Atop | Ubuntu | esm-apps/bionic | * |
| Atop | Ubuntu | esm-apps/focal | * |
| Atop | Ubuntu | esm-apps/jammy | * |
| Atop | Ubuntu | esm-apps/noble | * |
| Atop | Ubuntu | esm-apps/xenial | * |
| Atop | Ubuntu | esm-infra-legacy/trusty | * |
| Atop | Ubuntu | focal | * |
| Atop | Ubuntu | jammy | * |
| Atop | Ubuntu | noble | * |
| Atop | Ubuntu | oracular | * |
| Atop | Ubuntu | upstream | * |
While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, it can still lead to a denial of service. For example, if a server handles multiple simultaneous connections, and an assert() occurs in one single connection that causes all other connections to be dropped, this is a reachable assertion that leads to a denial of service.