First published: Fri May 03 2019(Updated: )
On BIG-IP 14.0.0-14.1.0.1, 13.0.0-13.1.1.4, 12.1.0-12.1.4, 11.6.1-11.6.3.4, and 11.5.2-11.5.8, DNS query TCP connections that are aborted before receiving a response from a DNS cache may cause TMM to restart.
Credit: f5sirt@f5.com
Affected Software | Affected Version | How to fix |
---|---|---|
F5 Access Policy Manager | >=11.5.2<11.5.9 | |
F5 Access Policy Manager | >=11.6.1<11.6.4 | |
F5 Access Policy Manager | >=12.1.0<12.1.4.1 | |
F5 Access Policy Manager | >=13.0.0<13.1.1.5 | |
F5 Access Policy Manager | >=14.0.0<14.1.0.2 | |
F5 BIG-IP Advanced Firewall Manager | >=11.5.2<11.5.9 | |
F5 BIG-IP Advanced Firewall Manager | >=11.6.1<11.6.4 | |
F5 BIG-IP Advanced Firewall Manager | >=12.1.0<12.1.4.1 | |
F5 BIG-IP Advanced Firewall Manager | >=13.0.0<13.1.1.5 | |
F5 BIG-IP Advanced Firewall Manager | >=14.0.0<14.1.0.2 | |
F5 BIG-IP Application Acceleration Manager | >=11.5.2<11.5.9 | |
F5 BIG-IP Application Acceleration Manager | >=11.6.1<11.6.4 | |
F5 BIG-IP Application Acceleration Manager | >=12.1.0<12.1.4.1 | |
F5 BIG-IP Application Acceleration Manager | >=13.0.0<13.1.1.5 | |
F5 BIG-IP Application Acceleration Manager | >=14.0.0<14.1.0.2 | |
F5 BIG-IP Link Controller | >=11.5.2<11.5.9 | |
F5 BIG-IP Link Controller | >=11.6.1<11.6.4 | |
F5 BIG-IP Link Controller | >=12.1.0<12.1.4.1 | |
F5 BIG-IP Link Controller | >=13.0.0<13.1.1.5 | |
F5 BIG-IP Link Controller | >=14.0.0<14.1.0.2 | |
F5 BIG-IP Policy Enforcement Manager | >=11.5.2<11.5.9 | |
F5 BIG-IP Policy Enforcement Manager | >=11.6.1<11.6.4 | |
F5 BIG-IP Policy Enforcement Manager | >=12.1.0<12.1.4.1 | |
F5 BIG-IP Policy Enforcement Manager | >=13.0.0<13.1.1.5 | |
F5 BIG-IP Policy Enforcement Manager | >=14.0.0<14.1.0.2 | |
F5 Application Security Manager | >=11.5.2<11.5.9 | |
F5 Application Security Manager | >=11.6.1<11.6.4 | |
F5 Application Security Manager | >=12.1.0<12.1.4.1 | |
F5 Application Security Manager | >=13.0.0<13.1.1.5 | |
F5 Application Security Manager | >=14.0.0<14.1.0.2 | |
Riverbed SteelApp Traffic Manager | >=11.5.2<11.5.9 | |
Riverbed SteelApp Traffic Manager | >=11.6.1<11.6.4 | |
Riverbed SteelApp Traffic Manager | >=12.1.0<12.1.4.1 | |
Riverbed SteelApp Traffic Manager | >=13.0.0<13.1.1.5 | |
Riverbed SteelApp Traffic Manager | >=14.0.0<14.1.0.2 | |
Riverbed SteelApp Traffic Manager | >=11.5.2<11.5.9 | |
Riverbed SteelApp Traffic Manager | >=11.6.1<11.6.4 | |
Riverbed SteelApp Traffic Manager | >=12.1.0<12.1.4.1 | |
Riverbed SteelApp Traffic Manager | >=13.0.0<13.1.1.5 | |
Riverbed SteelApp Traffic Manager | >=14.0.0<14.1.0.2 | |
F5 BIG-IP | >=11.5.2<11.5.9 | |
F5 BIG-IP | >=11.6.1<11.6.4 | |
F5 BIG-IP | >=12.1.0<12.1.4.1 | |
F5 BIG-IP | >=13.0.0<13.1.1.5 | |
F5 BIG-IP | >=14.0.0<14.1.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2019-6612 is classified as moderate due to the potential for TMM to restart, causing service disruption.
To fix CVE-2019-6612, upgrade affected F5 BIG-IP software versions to the latest non-vulnerable release.
CVE-2019-6612 affects F5 BIG-IP versions 11.5.2 to 11.5.8, 11.6.1 to 11.6.3.4, 12.1.0 to 12.1.4, 13.0.0 to 13.1.1.5, and 14.0.0 to 14.1.0.2.
CVE-2019-6612 impacts multiple components including the Access Policy Manager, Advanced Firewall Manager, and Local Traffic Manager among others.
As a temporary workaround for CVE-2019-6612, monitoring and managing DNS query configurations may help mitigate the issue until a patch can be applied.