The (1) ftpd and (2) ksu programs in (a) MIT Kerberos 5 (krb5) up to 1.5, and 1.4.x before 1.4.4, and (b) Heimdal 0.7.2 and earlier, do not
The (1) ftpd and (2) ksu programs in (a) MIT Kerberos 5 (krb5) up to 1.5, and 1.4.x before 1.4.4, and (b) Heimdal 0.7.2 and earlier, do not check return codes for setuid calls, which might allow local users to gain privileges by causing setuid to fail to drop privileges. NOTE: as of 20060808, it is not known whether an exploitable attack scenario exists for these issues.
- Published
- Aug 9, 2006
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 40th percentile
- CWE
- CWE-264
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
Affected systems
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- heimdal heimdalup to 0.7.2 inclusive
- mit kerberos 51.4
- mit kerberos 51.4.1
- mit kerberos 51.4.2
- mit kerberos 51.4.3
- mit kerberos 51.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | krb5 | before 1.4.3-9 | 1.4.3-9 |
| Debian:3.1 | krb5 | before 1.3.6-2sarge3 | 1.3.6-2sarge3 |
Same product
heimdal: all recordsOther highest-scoring records for the same primary product.
- CVE-2007-5939The gss_userok function in appl/ftp/ftpd/gss_userok.c in Heimdal 0.7.2 does not allocate memory for the ticketfile pointer before calling fr41Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:krb5 | 1.4.3-9 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:L/AC:L/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- ftp://ftp.pdc.kth.se/pub/heimdal/src/heimdal-0.7.2-setuid-patch.txt
- fedoranews.org/cms/node/2376
- secunia.com/advisories/21402
- secunia.com/advisories/21436
- secunia.com/advisories/21439
- secunia.com/advisories/21461
- secunia.com/advisories/21467
- secunia.com/advisories/21527
- secunia.com/advisories/21613
- secunia.com/advisories/23707
- security.gentoo.org/glsa/glsa-200608-21.xml
- securitytracker.com/id?1016664
- web.mit.edu/Kerberos/advisories/MITKRB5-SA-2006-001-setuid.txt
- www.debian.org/security/2006/dsa-1146
- www.gentoo.org/security/en/glsa/glsa-200608-15.xml
- www.kb.cert.org/vuls/id/401660
- www.novell.com/linux/security/advisories/2006_20_sr.html
- www.osvdb.org/27871
- www.osvdb.org/27872
- www.pdc.kth.se/heimdal/advisory/2006-08-08/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.