Skip to main content
Mallory
CriticalVulnerability

CVE-2002-1235: Kerberos kadmind Unchecked Request Length Buffer Overflow

Published Oct 25, 2002 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v2
EPSS15.1%97th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendors
Debian ProjectMassachusetts Institute of TechnologyKth
IdentifiersCVE-2002-1235CWE-130

CVE-2002-1235 is a remotely exploitable buffer overflow in the Kerberos 4-compatible administration-request parsing path, specifically kadm_ser_in. The affected daemons fail to validate a request length field before processing network-supplied administrative requests, allowing an oversized or inconsistent length value to overrun memory. Affected software includes MIT Kerberos 5 krb5-1.2.6 and earlier through kadmind4, KTH Kerberos 4 (eBones) before 1.2.1, and KTH Kerberos 5 (Heimdal) before 0.5.1 when built with Kerberos 4 support.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unauthenticated remote attacker can execute arbitrary code in the context of the Kerberos administration daemon. Because the daemon runs with root privileges, successful exploitation can yield root-level control of the KDC. Compromise of a master KDC can undermine the Kerberos realm and its dependent authentication infrastructure, including potential impersonation of Kerberos principals.

Mitigation

If you can’t patch tonight, do this now.

Disable Kerberos 4 compatibility support where it is not required. Disable the MIT kadmin4 service, or compile Heimdal kadmind without Kerberos 4 support. If patching cannot be completed immediately, stop and disable affected administration daemons and restrict access to Kerberos administration services to explicitly trusted hosts and networks.

Remediation

Patch, then assume compromise.

Apply vendor security updates. Upgrade MIT Kerberos to a corrected release or apply the patch from MIT krb5 Security Advisory 2002-002; update Heimdal to version 0.5.1 or later; and update eBones to version 1.2.1 or later. For affected FreeBSD systems and ports, apply the official security patch or upgrade to the corrected FreeBSD branch and updated Kerberos packages.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
KthKth Kerberos 4application
KthKth Kerberos 5application
Massachusetts Institute of TechnologyKerberos 5application
FAQ

Frequently asked questions

Is CVE-2002-1235 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2002-1235?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2002-1235.
Is there a patch for CVE-2002-1235?
Apply vendor security updates. Upgrade MIT Kerberos to a corrected release or apply the patch from MIT krb5 Security Advisory 2002-002; update Heimdal to version 0.5.1 or later; and update eBones to version 1.2.1 or later.
What products are affected by CVE-2002-1235?
Kth Kerberos 4, Kth Kerberos 5, Massachusetts Institute of Technology Kerberos 5, and Debian Project Debian Linux.
How severe is CVE-2002-1235?
CVE-2002-1235 has a CVSS v2 score of 10.0 (Critical) and an EPSS score of 15.1% (97th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.