CVE-2012-6110

NONECVSS 0.0

0.0

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.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 20.9%
KEV: Not listed

Published

September 29, 2014

Last Modified

May 6, 2026

References (8)

secalert@redhathttp://seclists.org/oss-sec/2013/q1/102
secalert@redhathttp://untroubled.org/bcron/NEWS
secalert@redhathttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686650
secalert@redhathttps://exchange.xforce.ibmcloud.com/vulnerabilities/81383
af854a3a-2127-422b-91ae-364da2661108http://seclists.org/oss-sec/2013/q1/102
af854a3a-2127-422b-91ae-364da2661108http://untroubled.org/bcron/NEWS
af854a3a-2127-422b-91ae-364da2661108https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686650
af854a3a-2127-422b-91ae-364da2661108https://exchange.xforce.ibmcloud.com/vulnerabilities/81383

Data Freshness Timeline

(refreshed 8× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

2026-06-08 14:14 UTCEPSS rescore
2026-06-07 15:22 UTCEPSS rescore
2026-06-06 13:45 UTCEPSS rescore
2026-06-06 13:45 UTCEPSS rescore
2026-06-05 22:44 UTCEPSS rescore
2026-06-05 22:44 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-02 20:10 UTCEPSS rescore
2026-06-02 20:10 UTCEPSS rescore
2026-06-01 13:49 UTCEPSS rescore
2026-06-01 13:49 UTCEPSS rescore
2026-05-31 22:28 UTCEPSS rescore
2026-05-31 22:28 UTCEPSS rescore
2026-05-31 00:14 UTCEPSS rescore
2026-05-31 00:14 UTCEPSS rescore
2026-05-29 13:41 UTCEPSS rescore
2026-05-29 13:41 UTCEPSS rescore
2026-05-28 16:31 UTCEG score recompute
2026-05-28 16:31 UTCGHSA enrichment

Frequently asked(4)

What is CVE-2012-6110?

CVE-2012-6110 is a none vulnerability published on September 29, 2014. 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.

When was CVE-2012-6110 disclosed?

CVE-2012-6110 was first published in the National Vulnerability Database on September 29, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2012-6110 actively exploited?

CVE-2012-6110 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2012-6110?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-6110, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2012-6110

Explore →

Is Your Infrastructure Affected by CVE-2012-6110?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2012-6110

📅 Published

🔄 Last Modified

🔗 References (8)