CVE-2018-5508: Medium severity F5 Big-ip Policy Enforcement Manager vulnerability
Published Apr 13, 2018
·Updated
On F5 BIG-IP PEM versions 13.0.0, 12.0.0-12.1.3.1, 11.6.0-11.6.2, 11.5.1-11.5.5, or 11.2.1, under certain conditions, TMM may crash when processing compressed data though a Virtual Server with an associated PEM profile using the content insertion option.
Affected Software
5 affected components
F5 Big-ip Policy Enforcement Manager>=11.5.1<=11.5.5
F5 Big-ip Policy Enforcement Manager>=11.6.0<=11.6.2
F5 Big-ip Policy Enforcement Manager>=12.0.0<=12.1.3
F5 Big-ip Policy Enforcement Manager=11.2.1
F5 Big-ip Policy Enforcement Manager=13.0.0
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
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2018-5508?
CVE-2018-5508 is categorized as a medium severity vulnerability.
2
How do I fix CVE-2018-5508?
To fix CVE-2018-5508, upgrade F5 BIG-IP PEM to a patched version beyond the affected versions listed.
3
What versions of F5 BIG-IP PEM are affected by CVE-2018-5508?
CVE-2018-5508 affects F5 BIG-IP PEM versions 11.2.1, 11.5.1-11.5.5, 11.6.0-11.6.2, and 12.0.0-12.1.3.1.
4
What happens when CVE-2018-5508 is exploited?
When exploited, CVE-2018-5508 can lead to a crash of the Traffic Management Microkernel (TMM) during the processing of compressed data.
5
Is there a workaround for CVE-2018-5508?
No official workarounds are provided for CVE-2018-5508; upgrading is the best option.