# CVE-2018-5709: Integer overflow in n/a

> An integer overflow in MIT Kerberos 5 allows attackers to corrupt database artifacts via crafted dump files, potentially compromising trusted data integrity.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-5709, CLEANSTART-2024-LS60465, DEBIAN-CVE-2018-5709, GHSA-9g2q-jwhw-j832, ROOT-OS-DEBIAN-12-CVE-2018-5709, UBUNTU-CVE-2018-5709

## What is CVE-2018-5709?

CVE-2018-5709 is a high-severity vulnerability in n/a, published on 16 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2018-5709?

It affects 1 product.


Products: Mit Kerberos.

## How do I fix CVE-2018-5709?

Apply the vendor's patch.

## Is CVE-2018-5709 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4212](https://insights.sbomify.com/CVE-2009-4212/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0523](https://insights.sbomify.com/CVE-2004-0523/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0283](https://insights.sbomify.com/CVE-2010-0283/): Denial of service in n/a (high 7.8)
- [CVE-2003-0138](https://insights.sbomify.com/CVE-2003-0138/): Auth bypass in n/a (high 7.5)
- [CVE-2003-0139](https://insights.sbomify.com/CVE-2003-0139/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5709 and fix it if it is affected.

What it is: CVE-2018-5709 is a high-severity vulnerability in n/a, published on 16 Jan 2018. 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-2018-5709 in the wild and no public exploit code.

Affected product: n/a. 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-2018-5709/ (Markdown: https://insights.sbomify.com/CVE-2018-5709/index.md)
```

## Sources

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

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