# CVE-2006-2607: Privilege escalation in n/a

> Local attackers can gain root privileges by exploiting unchecked setuid return codes in Vixie cron during resource limit failures.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2607, GHSA-m6pc-rv4c-hqmg, RHSA-2006:0539

## What is CVE-2006-2607?

CVE-2006-2607 is a high-severity vulnerability in n/a, published on 25 May 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

do_command.c in Vixie cron (vixie-cron) 4.1 does not check the return code of a setuid call, which might allow local users to gain root privileges if setuid fails in cases such as PAM failures or resource limits, as originally demonstrated by a program that exceeds the process limits as defined in /etc/security/limits.conf.

## Which versions are affected by CVE-2006-2607?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vixie-cron` | Red Hat:enterprise_linux:4::as | All versions | 4:4.1-44.EL4 |
| `vixie-cron-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 4:4.1-44.EL4 |
| `vixie-cron` | Red Hat:enterprise_linux:4::desktop | All versions | 4:4.1-44.EL4 |
| `vixie-cron-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 4:4.1-44.EL4 |
| `vixie-cron` | Red Hat:enterprise_linux:4::es | All versions | 4:4.1-44.EL4 |
| `vixie-cron-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 4:4.1-44.EL4 |
| `vixie-cron` | Red Hat:enterprise_linux:4::ws | All versions | 4:4.1-44.EL4 |
| `vixie-cron-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 4:4.1-44.EL4 |

Products: Paul Vixie Vixie Cron.

## How do I fix CVE-2006-2607?

Apply the vendor's patch.

## Is CVE-2006-2607 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0559](https://insights.sbomify.com/CVE-2001-0559/): Privilege escalation in n/a (high 7.2)
- [CVE-2001-0560](https://insights.sbomify.com/CVE-2001-0560/): Memory corruption in n/a (medium 4.6)
- [CVE-2000-1096](https://insights.sbomify.com/CVE-2000-1096/): Race condition in n/a (low 3.7)
- [CVE-2007-1856](https://insights.sbomify.com/CVE-2007-1856/): Misconfiguration in n/a (low 2.1)
- [CVE-2005-1038](https://insights.sbomify.com/CVE-2005-1038/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2607 and fix it if it is affected.

What it is: CVE-2006-2607 is a high-severity vulnerability in n/a, published on 25 May 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2607 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-2006-2607/ (Markdown: https://insights.sbomify.com/CVE-2006-2607/index.md)
```

## Sources

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

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