CVE-2012-6110

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2014-09-29 22:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:47 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 2.1 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2014-09-29 22:55 UTC

Last modified

2026-06-16 23:47 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-264

Record status

Modified

Affected

• Bcron Project Bcron Exec ≤ 0.09
• Bcron Project Bcron Exec 0.04
• Bcron Project Bcron Exec 0.05
• Bcron Project Bcron Exec 0.06
• Bcron Project Bcron Exec 0.07
• Bcron Project Bcron Exec 0.08

Attack profile CVSS 2.0 · 2.1

Attack vector

Local

Complexity

Low

Authentication

None

Confidentiality

None

Integrity

Partial

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2012-6110.md and follow it. Check whether this project is affected by CVE-2012-6110. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge