# CVE-2012-6097: Information disclosure in n/a

> Local attackers can exploit a file descriptor leak in cronie to read restricted system files like /etc/crontab.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/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:** No
- **Published:** 9 Apr 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r953-3vv9-m789

## What is CVE-2012-6097?

CVE-2012-6097 is a medium-severity vulnerability in n/a, published on 9 Apr 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

File descriptor leak in cronie 1.4.8, when running in certain environments, might allow local users to read restricted files, as demonstrated by reading /etc/crontab.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Fedorahosted Cronie.

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

No fix has been published for CVE-2012-6097 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-6097 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0424](https://insights.sbomify.com/CVE-2010-0424/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-6097 is a medium-severity vulnerability in n/a, published on 9 Apr 2013. 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-6097 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-6097/ (Markdown: https://insights.sbomify.com/CVE-2012-6097/index.md)
```

## Sources

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

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