CVE-1999-0768: Buffer Overflow

Published Aug 25, 1999
·
Updated

Buffer overflow in Vixie Cron on Red Hat systems via the MAILTO environmental variable.

Affected Software

5 affected components
redhat Linux=5.2
redhat Linux=6.0
SUSE SuSE Linux=6.0
SUSE SuSE Linux=6.1
redhat Linux=4.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Disable MAILTO support in cron or ensure MAILTO is not set from untrusted input; review and remove or sanitize MAILTO entries in system and user crontabs.

    Vixie Cron MAILTO environment variable handling = disabled or sanitize inputs

Event History

Aug 25, 1999
CVE Published
04:00 AM
Data Sourced
via NVD·04:00 AM
DescriptionSeverityAffected Software
Jan 18, 2000
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-1999-0768?

CVE-1999-0768 is classified as a high severity vulnerability due to its potential for remote code execution.

2

How do I fix CVE-1999-0768?

To fix CVE-1999-0768, update the Vixie Cron package to a version that is patched against this buffer overflow vulnerability.

3

Which systems are affected by CVE-1999-0768?

CVE-1999-0768 affects Red Hat Linux versions 4.2, 5.2, and 6.0, as well as SUSE Linux versions 6.0 and 6.1.

4

What is the impact of exploiting CVE-1999-0768?

Exploiting CVE-1999-0768 can allow an attacker to execute arbitrary code with the privileges of the cron service.

5

Is CVE-1999-0768 still relevant today?

While CVE-1999-0768 pertains to older systems, it highlights the importance of securing legacy software against vulnerabilities.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203