# CVE-2019-6630: Denial of service in F5 SSL Orchestrator

> Undisclosed traffic flow can cause the Traffic Management Microkernel to restart, leading to a denial of service on F5 SSL Orchestrator.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-478m-94c7-j94r

## What is CVE-2019-6630?

CVE-2019-6630 is a high-severity denial of service vulnerability in F5 SSL Orchestrator, published on 3 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2019-6630?

It affects 1 product.


Products: F5 Ssl Orchestrator.

## How do I fix CVE-2019-6630?

No fix has been published for CVE-2019-6630 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-6630 being exploited?

There is no known exploitation of CVE-2019-6630 in the wild and no public exploit code.

## Other vulnerabilities in F5 SSL Orchestrator

- [CVE-2019-6674](https://insights.sbomify.com/CVE-2019-6674/): Denial of service in SSL Orchestrator (high 7.5)
- [CVE-2019-6627](https://insights.sbomify.com/CVE-2019-6627/): Race condition in F5 SSL Orchestrator (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6630 and fix it if it is affected.

What it is: CVE-2019-6630 is a high-severity denial of service vulnerability in F5 SSL Orchestrator, published on 3 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6630 in the wild and no public exploit code.

Affected product: F5 SSL Orchestrator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-6630/ (Markdown: https://insights.sbomify.com/CVE-2019-6630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-6630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-6630
- OSV: https://osv.dev/vulnerability/CVE-2019-6630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-6630/
Summaries are generated and may contain mistakes; the official description above is the record.