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

> Local attackers can read sensitive core dump files from setuid programs if the suid_dumpable sysctl is enabled, exposing private data.

- **Severity:** Low 1.9 (`AV:L/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:** Yes
- **Published:** 3 Jul 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rph2-33pr-67ww

## What is CVE-2012-1106?

CVE-2012-1106 is a low-severity vulnerability in n/a, published on 3 Jul 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The C handler plug-in in Automatic Bug Reporting Tool (ABRT), possibly 2.0.8 and earlier, does not properly set the group (GID) permissions on core dump files for setuid programs when the sysctl fs.suid_dumpable option is set to 2, which allows local users to obtain sensitive information.

Weakness: CWE-264

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

It affects 1 product.


Products: Redhat Automatic Bug Reporting Tool.

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

Apply the vendor's patch.

## Is CVE-2012-1106 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-1869](https://insights.sbomify.com/CVE-2015-1869/): Path traversal in ABRT (high 7.8)
- [CVE-2015-3151](https://insights.sbomify.com/CVE-2015-3151/): Path traversal in ABRT (high 7.8)
- [CVE-2015-3159](https://insights.sbomify.com/CVE-2015-3159/): Privilege escalation in ABRT (high 7.8)
- [CVE-2015-3315](https://insights.sbomify.com/CVE-2015-3315/): Path traversal in n/a (high 7.8)
- [CVE-2015-3150](https://insights.sbomify.com/CVE-2015-3150/): Path traversal in ABRT (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1106 is a low-severity vulnerability in n/a, published on 3 Jul 2012. 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-1106 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-1106/ (Markdown: https://insights.sbomify.com/CVE-2012-1106/index.md)
```

## Sources

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

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