# CVE-2007-3999: Memory corruption in n/a

> Remote attackers can trigger a stack-based buffer overflow in the Kerberos RPC library, potentially causing denial of service or arbitrary code execution.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-3999, DSA-1368-1, GHSA-62qg-wq9p-p6p2, RHSA-2007:0913

## What is CVE-2007-3999?

CVE-2007-3999 is a critical memory corruption vulnerability in Mit Kerberos 5, published on 5 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in the svcauth_gss_validate function in lib/rpc/svc_auth_gss.c in the RPCSEC_GSS RPC library (librpcsecgss) in MIT Kerberos 5 (krb5) 1.4 through 1.6.2, as used by the Kerberos administration daemon (kadmind) and some third-party applications that use krb5, allows remote attackers to cause a denial of service (daemon crash) and probably execute arbitrary code via a long string in an RPC message.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2007-3999?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nfs-utils-lib` | Red Hat:enterprise_linux:4::as | All versions | 0:1.0.6-8.z1 |
| `nfs-utils-lib-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.0.6-8.z1 |
| `nfs-utils-lib-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:1.0.6-8.z1 |
| `nfs-utils-lib` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.0.6-8.z1 |
| `nfs-utils-lib-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.0.6-8.z1 |
| `nfs-utils-lib-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.0.6-8.z1 |
| `nfs-utils-lib` | Red Hat:enterprise_linux:4::es | All versions | 0:1.0.6-8.z1 |
| `nfs-utils-lib-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.0.6-8.z1 |
| `nfs-utils-lib-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:1.0.6-8.z1 |
| `nfs-utils-lib` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.0.6-8.z1 |
| `nfs-utils-lib-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.0.6-8.z1 |
| `nfs-utils-lib-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.0.6-8.z1 |

Products: Mit Kerberos 5.

## How do I fix CVE-2007-3999?

Upgrade to a fixed version.

## Is CVE-2007-3999 being exploited?

There is no known exploitation of CVE-2007-3999 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-2000-0514](https://insights.sbomify.com/CVE-2000-0514/): Missing authorization in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3999 and fix it if it is affected.

What it is: CVE-2007-3999 is a critical memory corruption vulnerability in Mit Kerberos 5, published on 5 Sep 2007. 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-2007-3999 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-2007-3999/ (Markdown: https://insights.sbomify.com/CVE-2007-3999/index.md)
```

## Sources

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

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