CVE-2012-6110: bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when runnin...

Security readout for executives and security teams

bcron before 0.10 could leave temporary job-output files accessible to running cron jobs. A local user might abuse those open file handles to alter job-related files and send spam. This is mainly a shared-host or multi-user server risk, not a remote internet-facing flaw based on the provided sources. Exposure is likely limited to systems using bcron, especially versions before 0.10, where untrusted or semi-trusted local users can run cron jobs. The bundle does not identify specific distributions, CPEs, or default installations beyond bcron itself. Prioritize remediation on shared servers, hosting environments, and systems where non-admin users run scheduled jobs. For single-user or tightly controlled servers, urgency is lower but still worth fixing during normal patch cycles. Mitigation focus: Upgrade bcron to 0.10 or later where vendor packages are available.; Check distribution advisories when package versions include backported fixes.; Restrict local shell and cron access on shared hosts until remediated..

Prepared

Jun 14, 2026, 06:54 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.