On BIG-IP versions 16.1.x before 16.1.3.3, 15.1.x before 15.1.8.1, 14.1.x before 14.1.5.3, and all versions of 13.1.x, when a SIP profile is configured on a Message Routing type virtual server, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Weakness
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Big-ip_access_policy_manager | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_access_policy_manager | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_access_policy_manager | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_access_policy_manager | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
| Big-ip_advanced_firewall_manager | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_advanced_firewall_manager | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_advanced_firewall_manager | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_advanced_firewall_manager | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
| Big-ip_analytics | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_analytics | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_analytics | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_analytics | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
| Big-ip_application_acceleration_manager | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_application_acceleration_manager | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_application_acceleration_manager | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_application_acceleration_manager | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
| Big-ip_application_security_manager | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_application_security_manager | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_application_security_manager | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_application_security_manager | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
| Big-ip_ddos_hybrid_defender | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_ddos_hybrid_defender | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_ddos_hybrid_defender | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_ddos_hybrid_defender | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
| Big-ip_domain_name_system | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_domain_name_system | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_domain_name_system | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_domain_name_system | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
| Big-ip_fraud_protection_service | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_fraud_protection_service | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_fraud_protection_service | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_fraud_protection_service | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
| Big-ip_link_controller | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_link_controller | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_link_controller | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_link_controller | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
| Big-ip_local_traffic_manager | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_local_traffic_manager | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_local_traffic_manager | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_local_traffic_manager | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
| Big-ip_policy_enforcement_manager | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_policy_enforcement_manager | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_policy_enforcement_manager | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_policy_enforcement_manager | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
| Big-ip_ssl_orchestrator | F5 | 13.1.0 (including) | 13.1.5 (including) |
| Big-ip_ssl_orchestrator | F5 | 14.1.0 (including) | 14.1.5.3 (excluding) |
| Big-ip_ssl_orchestrator | F5 | 15.1.0 (including) | 15.1.8.1 (excluding) |
| Big-ip_ssl_orchestrator | F5 | 16.1.0 (including) | 16.1.3.3 (excluding) |
Potential Mitigations
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
- D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
- Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
- For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].