Vulnerabilities > F5 > BIG IP Policy Enforcement Manager > 11.6.2
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2018-04-13 | CVE-2018-5508 | Unspecified vulnerability in F5 Big-Ip Policy Enforcement Manager 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. | 5.9 |
| 2018-04-13 | CVE-2018-5507 | Unspecified vulnerability in F5 products On F5 BIG-IP versions 13.0.0, 12.1.0-12.1.3.1, 11.6.1-11.6.2, or 11.5.1-11.5.5, vCMP guests running on VIPRION 2100, 4200 and 4300 series blades cannot correctly decrypt ciphertext from established SSL sessions with small MTU. | 7.5 |
| 2018-04-13 | CVE-2017-6155 | Unspecified vulnerability in F5 products On F5 BIG-IP 13.0.0, 12.0.0-12.1.3.1, 11.6.0-11.6.2, 11.4.1-11.5.5, or 11.2.1, malformed SPDY or HTTP/2 requests may result in a disruption of service to TMM. | 7.5 |
| 2018-04-13 | CVE-2017-6148 | Improper Input Validation vulnerability in F5 products Responses to SOCKS proxy requests made through F5 BIG-IP version 13.0.0, 12.0.0-12.1.3.1, 11.6.1-11.6.2, or 11.5.1-11.5.5 may cause a disruption of services provided by TMM. | 7.5 |
| 2018-03-01 | CVE-2018-5501 | Resource Exhaustion vulnerability in F5 products In some circumstances, on F5 BIG-IP systems running 13.0.0, 12.1.0 - 12.1.3.1, any 11.6.x or 11.5.x release, or 11.2.1, TCP DNS profile allows excessive buffering due to lack of flow control. | 5.9 |
| 2018-03-01 | CVE-2018-5500 | Resource Exhaustion vulnerability in F5 products On F5 BIG-IP systems running 13.0.0, 12.1.0 - 12.1.3.1, or 11.6.1 - 11.6.2, every Multipath TCP (MCTCP) connection established leaks a small amount of memory. | 5.9 |
| 2018-02-06 | CVE-2017-6169 | Improper Input Validation vulnerability in F5 Big-Ip Policy Enforcement Manager In versions 13.0.0, 12.0.0-12.1.3, or 11.6.0-11.6.2, an F5 BIG-IP virtual server using the URL categorization feature may cause the Traffic Management Microkernel (TMM) to produce a core file when it receives malformed URLs during categorization. | 6.8 |