In Eclipse Mosquitto 1.4.15 and earlier, a Memory Leak vulnerability was found within the Mosquitto Broker. Unauthenticated clients can send crafted CONNECT packets which could cause a denial of service in the Mosquitto Broker.
Weakness
The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Mosquitto |
Eclipse |
* |
1.4.15 (including) |
| Mosquitto |
Ubuntu |
artful |
* |
| Mosquitto |
Ubuntu |
bionic |
* |
| Mosquitto |
Ubuntu |
cosmic |
* |
| Mosquitto |
Ubuntu |
esm-infra-legacy/trusty |
* |
| Mosquitto |
Ubuntu |
trusty |
* |
| Mosquitto |
Ubuntu |
trusty/esm |
* |
| Mosquitto |
Ubuntu |
upstream |
* |
| Mosquitto |
Ubuntu |
xenial |
* |
Potential Mitigations
- Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
- For example, glibc in Linux provides protection against free of invalid pointers.
- When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
- To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.
References