A vulnerability in the endpoint software of Cisco AMP for Endpoints and Clam AntiVirus could allow an authenticated, local attacker to cause the running software to delete arbitrary files on the system. The vulnerability is due to a race condition that could occur when scanning malicious files. An attacker with local shell access could exploit this vulnerability by executing a script that could trigger the race condition. A successful exploit could allow the attacker to delete arbitrary files on the system that the attacker would not normally have privileges to delete, producing system instability or causing the endpoint software to stop working.
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Advanced_malware_protection_for_endpoints | Cisco | * | 1.12.4 (excluding) |
| Clam_antivirus | Cisco | * | 0.102.4 (excluding) |
| Clamav | Ubuntu | bionic | * |
| Clamav | Ubuntu | esm-infra-legacy/trusty | * |
| Clamav | Ubuntu | esm-infra/bionic | * |
| Clamav | Ubuntu | esm-infra/focal | * |
| Clamav | Ubuntu | esm-infra/xenial | * |
| Clamav | Ubuntu | focal | * |
| Clamav | Ubuntu | trusty | * |
| Clamav | Ubuntu | trusty/esm | * |
| Clamav | Ubuntu | upstream | * |
| Clamav | Ubuntu | xenial | * |
A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:
A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.