# CVE-2020-6098: Memory corruption in freeDiameter

> An attacker can cause a denial of service in freeDiameter by sending a specially crafted Diameter request that triggers memory corruption.

- **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:** Yes
- **Published:** 28 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-6098, GHSA-wcwj-33h6-vxqv, UBUNTU-CVE-2020-6098

## What is CVE-2020-6098?

CVE-2020-6098 is a high-severity memory corruption vulnerability in freeDiameter, published on 28 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An exploitable denial of service vulnerability exists in the freeDiameter functionality of freeDiameter 1.3.2. A specially crafted Diameter request can trigger a memory corruption resulting in denial-of-service. An attacker can send a malicious packet to trigger this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write), CWE-191 (Integer Underflow (Wrap or Wraparound))

## Which versions are affected by CVE-2020-6098?

It affects 1 product.


Products: Freediameter Freediameter.

## How do I fix CVE-2020-6098?

Apply the vendor's patch.

## Is CVE-2020-6098 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6098 and fix it if it is affected.

What it is: CVE-2020-6098 is a high-severity memory corruption vulnerability in freeDiameter, published on 28 Jul 2020. 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-2020-6098 in the wild and no public exploit code.

Affected product: freeDiameter. 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-2020-6098/ (Markdown: https://insights.sbomify.com/CVE-2020-6098/index.md)
```

## Sources

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

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