CVE-1999-0340: Slackware Linux buffer overflow in crond

CVE-1999-0340 · Severity: high · CVSS 7.2 · Published 1997-12-01

A security vulnerability exists in the task scheduling service (crond) of Slackware Linux. This service is responsible for running automated background tasks at specific times. An attacker with local access to the system could exploit this flaw to gain full administrative control (root access), potentially leading to complete system compromise and data theft.

Technologies: Slackware Linux. Vendors: Slackware.

Quick answers

Is CVE-1999-0340 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-1999-0340 being exploited in the wild.
How severe is CVE-1999-0340?
High severity, with a CVSS score of 7.2, published 1 December 1997.
Which products and versions are affected?
Slackware Slackware Linux Unknown.
Is there a fix for CVE-1999-0340?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-1999-0340 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-1999-0340?
Check whether you run Slackware Linux. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A buffer overflow vulnerability exists within the crond daemon in Slackware Linux. The flaw is triggered during the processing of specific inputs, though the exact vulnerable parameter is not specified in the legacy advisory. Because crond typically runs with elevated privileges to manage system-wide tasks, a local attacker can exploit this memory corruption to execute arbitrary code with root permissions. This allows for a complete privilege escalation from a standard user to the system administrator. The vulnerability is accessible to any user with local shell access.

Affected products

  • Slackware Slackware Linux Unknown

Timeline

  • 1997-12-01: disclosed: Initial publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.