On BIG-IP 11.5.1-11.6.3.4, 12.1.0-12.1.3.7, 13.0.0-13.1.1.3, and 14.0.0-14.0.0.2, when processing certain SNMP requests with a request-id of 0, the snmpd process may leak a small amount of memory.
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 |
| Big-ip_access_policy_manager |
F5 |
11.5.1 (including) |
11.6.3.4 (including) |
| Big-ip_access_policy_manager |
F5 |
12.1.0 (including) |
12.1.3.7 (including) |
| Big-ip_access_policy_manager |
F5 |
13.0.0 (including) |
13.1.1.3 (including) |
| Big-ip_access_policy_manager |
F5 |
14.0.0 (including) |
14.0.0.2 (including) |
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