# CVE-2019-6674: Denial of service in SSL Orchestrator

> Attackers can crash the Traffic Management Microkernel in F5 SSL Orchestrator when using service-chaining configurations, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 27 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vqmr-6f7c-q88q

## What is CVE-2019-6674?

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

### Official description

On F5 SSL Orchestrator 15.0.0-15.0.1 and 14.0.0-14.1.2, TMM may crash when processing SSLO data in a service-chaining configuration.

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

It affects 1 product.


Products: F5 Ssl Orchestrator.

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

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

## Is CVE-2019-6674 being exploited?

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

## Other vulnerabilities in F5 SSL Orchestrator

- [CVE-2019-6630](https://insights.sbomify.com/CVE-2019-6630/): Denial of service in F5 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-6674 and fix it if it is affected.

What it is: CVE-2019-6674 is a high-severity denial of service vulnerability in F5 SSL Orchestrator, published on 27 Nov 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-6674 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-6674/ (Markdown: https://insights.sbomify.com/CVE-2019-6674/index.md)
```

## Sources

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

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