A memory leak in OpenVPN version 2.5.0 through 2.5.11, 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote attackers with a valid tls-crypt-v2 client key to potentially cause a denial of service
Weakness
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Openvpn | Openvpn | 2.5.0 (including) | 2.5.11 (including) |
| Openvpn | Openvpn | 2.6.0 (including) | 2.6.21 (excluding) |
| Openvpn | Openvpn | 2.7 (including) | 2.7.5 (excluding) |
| Openvpn | Ubuntu | devel | * |
| Openvpn | Ubuntu | jammy | * |
| Openvpn | Ubuntu | noble | * |
| Openvpn | Ubuntu | questing | * |
| Openvpn | Ubuntu | resolute | * |
| Openvpn | Ubuntu | upstream | * |
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.