CVE-2019-6630
First published: Wed Jul 03 2019(Updated: )
On F5 SSL Orchestrator 14.1.0-14.1.0.5 and 14.0.0-14.0.0.4, undisclosed traffic flow may cause TMM to restart under certain circumstances.
Credit: f5sirt@f5.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| F5 SSL Orchestrator | >=14.0.0<14.0.0.5 | |
| F5 SSL Orchestrator | >=14.1.0<14.1.0.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is CVE-2019-6630?
CVE-2019-6630 is a vulnerability in F5 SSL Orchestrator versions 14.1.0-14.1.0.5 and 14.0.0-14.0.0.4 that allows undisclosed traffic flow to cause the Traffic Management Microkernel (TMM) to restart.
How does CVE-2019-6630 impact F5 SSL Orchestrator?
CVE-2019-6630 can cause the TMM in F5 SSL Orchestrator to restart under certain circumstances when undisclosed traffic flow occurs.
What is the severity of CVE-2019-6630?
CVE-2019-6630 has a severity rating of 7.5 (high).
Which versions of F5 SSL Orchestrator are affected by CVE-2019-6630?
Versions 14.1.0-14.1.0.5 and 14.0.0-14.0.0.4 of F5 SSL Orchestrator are affected by CVE-2019-6630.
How can I mitigate CVE-2019-6630 in F5 SSL Orchestrator?
To mitigate CVE-2019-6630, it is recommended to upgrade to version 14.1.0.6 or higher for F5 SSL Orchestrator.
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/description
- agent/tags
- agent/last-modified-date
- agent/author
- agent/severity
- agent/first-publish-date
- agent/event
- vendor/f5
- canonical/f5 ssl orchestrator
- version/f5 ssl orchestrator/14.0.0
- version/f5 ssl orchestrator/14.1.0