CVE-2019-6592: Critical severity f5 access policy manager vulnerability
Published Feb 26, 2019
·Updated
On BIG-IP 14.1.0-14.1.0.1, TMM may restart and produce a core file when validating SSL certificates in client SSL or server SSL profiles.
Affected Software
12 affected components
F5 BIG-IP Access Policy Manager>=14.1.0<=14.1.0.1
F5 Big-ip Local Traffic Manager>=14.1.0<=14.1.0.1
F5 BIG-IP Advanced Firewall Manager>=14.1.0<=14.1.0.1
F5 BIG-IP Analytics>=14.1.0<=14.1.0.1
F5 BIG-IP Application Security Manager>=14.1.0<=14.1.0.1
F5 Big-ip Domain Name System>=14.1.0<=14.1.0.1
F5 BIG-IP Edge Gateway>=14.1.0<=14.1.0.1
F5 Big-ip Fraud Protection Service>=14.1.0<=14.1.0.1
F5 Big-ip Global Traffic Manager>=14.1.0<=14.1.0.1
F5 Big-ip Link Controller>=14.1.0<=14.1.0.1
F5 Big-ip Policy Enforcement Manager>=14.1.0<=14.1.0.1
F5 Big-ip Webaccelerator>=14.1.0<=14.1.0.1
Event History
Feb 26, 2019
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
DescriptionWeakness
Data Sourced
via NVD·03:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-6592?
CVE-2019-6592 is considered a high severity vulnerability due to its potential impact on system stability.
2
How do I fix CVE-2019-6592?
To fix CVE-2019-6592, you should upgrade to a patched version of F5 BIG-IP software that eliminates the vulnerability.
3
What are the affected versions of CVE-2019-6592?
CVE-2019-6592 affects F5 BIG-IP versions from 14.1.0 to 14.1.0.1.
4
What kind of impact can CVE-2019-6592 have on my system?
CVE-2019-6592 can cause the Traffic Management Microkernel (TMM) to restart, potentially interrupting service.
5
Is CVE-2019-6592 specific to any particular F5 BIG-IP module?
Yes, CVE-2019-6592 is applicable across multiple F5 BIG-IP modules, including Access Policy Manager and Local Traffic Manager.