# CVE-2012-6110: Missing authorization in n/a

> Local attackers can modify cron job files and send spam by accessing open file descriptors in bcron-exec.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-6110, GHSA-j9p5-9mcj-v7gh

## What is CVE-2012-6110?

CVE-2012-6110 is a low-severity missing authorization vulnerability in n/a, published on 29 Sep 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-264

## Which versions are affected by CVE-2012-6110?

It affects 1 product.


Products: Bcron Project Bcron Exec.

## How do I fix CVE-2012-6110?

Upgrade to a fixed version.

## Is CVE-2012-6110 being exploited?

There is no known exploitation of CVE-2012-6110 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6110 and fix it if it is affected.

What it is: CVE-2012-6110 is a low-severity missing authorization vulnerability in n/a, published on 29 Sep 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-6110 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-6110/ (Markdown: https://insights.sbomify.com/CVE-2012-6110/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-6110
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-6110
- OSV: https://osv.dev/vulnerability/CVE-2012-6110

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-6110/
Summaries are generated and may contain mistakes; the official description above is the record.