# CVE-2016-3119: Null dereference in n/a

> Remote authenticated users can crash the Kerberos KDC daemon via a crafted request due to a NULL pointer dereference in the LDAP KDB module.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2016
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2016-3119, DEBIAN-CVE-2016-3119, GHSA-qq9x-4x4m-294x, MGASA-2016-0123, SUSE-SU-2016:0994-1, SUSE-SU-2016:1088-1, UBUNTU-CVE-2016-3119

## What is CVE-2016-3119?

CVE-2016-3119 is a medium-severity vulnerability in Mit Kerberos 5, published on 26 Mar 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The process_db_args function in plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in the LDAP KDB module in kadmind in MIT Kerberos 5 (aka krb5) through 1.13.4 and 1.14.x through 1.14.1 mishandles the DB argument, which allows remote authenticated users to cause a denial of service (NULL pointer dereference and daemon crash) via a crafted request to modify a principal.

## Which versions are affected by CVE-2016-3119?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `krb5` | SUSE:Linux Enterprise Desktop 12 | All versions | 1.12.1-28.1 |
| `krb5` | SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 1.12.1-28.1 |
| `krb5` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 1.6.3-133.49.109.1 |
| `krb5` | SUSE:Linux Enterprise Server 12 | All versions | 1.12.1-28.1 |
| `krb5` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 1.12.1-28.1 |
| `krb5` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 1.6.3-133.49.109.1 |
| `krb5` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 1.12.1-28.1 |
| `krb5` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.12.1-28.1 |
| `krb5` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 1.6.3-133.49.109.1 |
| `krb5` | SUSE:Linux Enterprise Software Development Kit 12 | All versions | 1.12.1-28.1 |
| `krb5` | SUSE:Linux Enterprise Software Development Kit 12 SP1 | All versions | 1.12.1-28.1 |

Products: Mit Kerberos 5, Opensuse Leap, Opensuse Opensuse.

## How do I fix CVE-2016-3119?

Apply the vendor's patch.

## Is CVE-2016-3119 being exploited?

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

## Other vulnerabilities in Mit Kerberos 5

- [CVE-2011-0285](https://insights.sbomify.com/CVE-2011-0285/): Use after free in n/a (critical 10.0)
- [CVE-2008-0947](https://insights.sbomify.com/CVE-2008-0947/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5902](https://insights.sbomify.com/CVE-2007-5902/): Integer overflow in n/a (critical 10.0)
- [CVE-2007-4743](https://insights.sbomify.com/CVE-2007-4743/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-3999](https://insights.sbomify.com/CVE-2007-3999/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-3119 and fix it if it is affected.

What it is: CVE-2016-3119 is a medium-severity vulnerability in Mit Kerberos 5, published on 26 Mar 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-3119 in the wild and no public exploit code.

Affected product: Mit Kerberos 5. 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-2016-3119/ (Markdown: https://insights.sbomify.com/CVE-2016-3119/index.md)
```

## Sources

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

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