An issue was discovered in NFStream 5.2.0. Because some allocated modules are not correctly freed, if the nfstream object is directly destroyed without being used after it is created, it will cause a memory leak that may result in a local denial of service (DoS).
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 |
| Nfstream |
Nfstream |
5.2.0 (including) |
5.2.0 (including) |
| Ndpi |
Ubuntu |
bionic |
* |
| Ndpi |
Ubuntu |
groovy |
* |
| Ndpi |
Ubuntu |
hirsute |
* |
| Ndpi |
Ubuntu |
impish |
* |
| Ndpi |
Ubuntu |
kinetic |
* |
| Ndpi |
Ubuntu |
lunar |
* |
| Ndpi |
Ubuntu |
mantic |
* |
| Ndpi |
Ubuntu |
trusty |
* |
| Ndpi |
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