When handling a libprocess message wrapped in an HTTP request, libprocess in Apache Mesos before 1.1.3, 1.2.x before 1.2.2, 1.3.x before 1.3.1, and 1.4.0-dev crashes if the request path is empty, because the parser assumes the request path always starts with /. A malicious actor can therefore cause a denial of service of Mesos masters rendering the Mesos-controlled cluster inoperable.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Mesos | Apache | * | 1.1.2 (including) |
| Mesos | Apache | 1.2.0 (including) | 1.2.0 (including) |
| Mesos | Apache | 1.2.1 (including) | 1.2.1 (including) |
| Mesos | Apache | 1.3.0 (including) | 1.3.0 (including) |
| Mesos | Apache | 1.3.1 (including) | 1.3.1 (including) |
| Mesos | Apache | 1.4.0-dev (including) | 1.4.0-dev (including) |