CVE-2012-6110: bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a
CVE-2012-6110 is a low-severity flaw (CVSS 2.1) affecting bcron exec. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 2.1 (Low) |
| EPSS exploit chance | 0.4% (top 63%) |
| CISA exploited list | No |
| Weakness | CWE-264 |
| Published | 2014-09-29 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2012-6110?
bcron exec: upgrade to newer than 0.09. Exact commands for each OS are on this page.
Is CVE-2012-6110 being exploited?
CVE-2012-6110 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2012-6110 affect?
CVE-2012-6110 affects bcron exec. Severity is low (CVSS 2.1). bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.
How urgent is CVE-2012-6110?
Priority 22/100. Public exploit reference