CVE-2006-2607: High severity Paul Vixie Vixie Cron vulnerability

Published May 25, 2006

Updated

docommand.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.

Affected Software

1 affected component

Paul Vixie Vixie Cron=4.1

Remediation

Patch Available

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178431

Event History

May 25, 2006

CVE Published

via MITRE·08:00 PM

Data Sourced

via MITRE·08:00 PM

Description

Frequently Asked Questions

What is the severity of CVE-2006-2607?

CVE-2006-2607 has a high severity rating due to its potential to allow local users to gain root privileges.

How do I fix CVE-2006-2607?

To fix CVE-2006-2607, update Vixie cron to the latest version that addresses this vulnerability.

Which software is affected by CVE-2006-2607?

CVE-2006-2607 specifically affects Vixie cron version 4.1.

What are the possible consequences of CVE-2006-2607?

The possible consequence of CVE-2006-2607 is unauthorized escalation of privileges, allowing local users to execute commands with root access.

Is CVE-2006-2607 still relevant today?

While CVE-2006-2607 pertains to an older software version, it remains relevant for systems that still run Vixie cron 4.1.