# CVE-2019-10028: Denial of service in Dial Reference Source Code Repo (https://github.com/Netflix/dial-reference)

> A denial of service vulnerability exists in the Netflix DIAL reference source code, affecting implementations using code prior to June 2019.

- **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:** 21 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q2fh-c6r8-p2jc

## What is CVE-2019-10028?

CVE-2019-10028 is a high-severity denial of service vulnerability in Dial Reference Source Code Repo (https://github.com/Netflix/dial-reference), published on 21 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Denial of Service (DOS) in Dial Reference Source Code Used before June 18th, 2019.

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

It affects 1 product.


Products: Netflix Dial Reference.

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

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

## Is CVE-2019-10028 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10028 is a high-severity denial of service vulnerability in Dial Reference Source Code Repo (https://github.com/Netflix/dial-reference), published on 21 Jun 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-10028 in the wild and no public exploit code.

Affected product: Dial Reference Source Code Repo (https://github.com/Netflix/dial-reference). 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-10028/ (Markdown: https://insights.sbomify.com/CVE-2019-10028/index.md)
```

## Sources

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

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