CVE-2018-5510: Input Validation
Published Apr 13, 2018
·Updated
On F5 BIG-IP 11.5.4 HF4-11.5.5, the Traffic Management Microkernel (TMM) may restart when processing a specific sequence of packets on IPv6 virtual servers.
Affected Software
78 affected components
F5 Big-ip Local Traffic Manager=11.5.4
F5 Big-ip Local Traffic Manager=11.5.4-hf1
F5 Big-ip Local Traffic Manager=11.5.4-hf2
F5 Big-ip Local Traffic Manager=11.5.4-hf3
F5 Big-ip Local Traffic Manager=11.5.4-hf4
F5 Big-ip Local Traffic Manager=11.5.5
F5 Big-ip Application Acceleration Manager=11.5.4
F5 Big-ip Application Acceleration Manager=11.5.4-hf1
F5 Big-ip Application Acceleration Manager=11.5.4-hf2
F5 Big-ip Application Acceleration Manager=11.5.4-hf3
F5 Big-ip Application Acceleration Manager=11.5.4-hf4
F5 Big-ip Application Acceleration Manager=11.5.5
F5 BIG-IP Advanced Firewall Manager=11.5.4
F5 BIG-IP Advanced Firewall Manager=11.5.4-hf1
F5 BIG-IP Advanced Firewall Manager=11.5.4-hf2
F5 BIG-IP Advanced Firewall Manager=11.5.4-hf3
F5 BIG-IP Advanced Firewall Manager=11.5.4-hf4
F5 BIG-IP Advanced Firewall Manager=11.5.5
F5 BIG-IP Analytics=11.5.4
F5 BIG-IP Analytics=11.5.4-hf1
F5 BIG-IP Analytics=11.5.4-hf2
F5 BIG-IP Analytics=11.5.4-hf3
F5 BIG-IP Analytics=11.5.4-hf4
F5 BIG-IP Analytics=11.5.5
F5 BIG-IP Access Policy Manager=11.5.4
F5 BIG-IP Access Policy Manager=11.5.4-hf1
F5 BIG-IP Access Policy Manager=11.5.4-hf2
F5 BIG-IP Access Policy Manager=11.5.4-hf3
F5 BIG-IP Access Policy Manager=11.5.4-hf4
F5 BIG-IP Access Policy Manager=11.5.5
F5 BIG-IP Application Security Manager=11.5.4
F5 BIG-IP Application Security Manager=11.5.4-hf1
F5 BIG-IP Application Security Manager=11.5.4-hf2
F5 BIG-IP Application Security Manager=11.5.4-hf3
F5 BIG-IP Application Security Manager=11.5.4-hf4
F5 BIG-IP Application Security Manager=11.5.5
F5 BIG-IP Edge Gateway=11.5.4
F5 BIG-IP Edge Gateway=11.5.4-hf1
F5 BIG-IP Edge Gateway=11.5.4-hf2
F5 BIG-IP Edge Gateway=11.5.4-hf3
F5 BIG-IP Edge Gateway=11.5.4-hf4
F5 BIG-IP Edge Gateway=11.5.5
F5 Big-ip Global Traffic Manager=11.5.4
F5 Big-ip Global Traffic Manager=11.5.4-hf1
F5 Big-ip Global Traffic Manager=11.5.4-hf2
F5 Big-ip Global Traffic Manager=11.5.4-hf3
F5 Big-ip Global Traffic Manager=11.5.4-hf4
F5 Big-ip Global Traffic Manager=11.5.5
F5 Big-ip Link Controller=11.5.4
F5 Big-ip Link Controller=11.5.4-hf1
F5 Big-ip Link Controller=11.5.4-hf2
F5 Big-ip Link Controller=11.5.4-hf3
F5 Big-ip Link Controller=11.5.4-hf4
F5 Big-ip Link Controller=11.5.5
F5 Big-ip Policy Enforcement Manager=11.5.4
F5 Big-ip Policy Enforcement Manager=11.5.4-hf1
F5 Big-ip Policy Enforcement Manager=11.5.4-hf2
F5 Big-ip Policy Enforcement Manager=11.5.4-hf3
F5 Big-ip Policy Enforcement Manager=11.5.4-hf4
F5 Big-ip Policy Enforcement Manager=11.5.5
F5 Big-ip Webaccelerator=11.5.4
F5 Big-ip Webaccelerator=11.5.4-hf1
F5 Big-ip Webaccelerator=11.5.4-hf2
F5 Big-ip Webaccelerator=11.5.4-hf3
F5 Big-ip Webaccelerator=11.5.4-hf4
F5 Big-ip Webaccelerator=11.5.5
F5 Big-ip Websafe=11.5.4
F5 Big-ip Websafe=11.5.4-hf1
F5 Big-ip Websafe=11.5.4-hf2
F5 Big-ip Websafe=11.5.4-hf3
F5 Big-ip Websafe=11.5.4-hf4
F5 Big-ip Websafe=11.5.5
F5 Big-ip Domain Name System=11.5.4
F5 Big-ip Domain Name System=11.5.4-hf1
F5 Big-ip Domain Name System=11.5.4-hf2
F5 Big-ip Domain Name System=11.5.4-hf3
F5 Big-ip Domain Name System=11.5.4-hf4
F5 Big-ip Domain Name System=11.5.5
Event History
Apr 13, 2018
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionWeakness
Data Sourced
via NVD·01:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2018-5510?
CVE-2018-5510 is classified as a high severity vulnerability due to its potential to disrupt the operation of the F5 BIG-IP system.
2
How do I fix CVE-2018-5510?
To fix CVE-2018-5510, you should upgrade your F5 BIG-IP system to the latest version that is not affected by this vulnerability.
3
What systems are affected by CVE-2018-5510?
CVE-2018-5510 affects F5 BIG-IP Local Traffic Manager versions 11.5.4 through 11.5.5 and various other related F5 products.
4
What are the symptoms of CVE-2018-5510 exploitation?
The exploitation of CVE-2018-5510 may cause the Traffic Management Microkernel (TMM) to restart unexpectedly when processing specific packet sequences.
5
Is there a workaround for CVE-2018-5510?
While upgrading is the recommended fix for CVE-2018-5510, specific configuration changes can mitigate its impact until an upgrade can be applied.