# CVE-2015-1870: Information disclosure in n/a

> Local attackers can read sensitive system logs due to insecure file permissions in ABRT event scripts.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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:** 26 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v6ww-8wv5-ggw9

## What is CVE-2015-1870?

CVE-2015-1870 is a medium-severity vulnerability in n/a, published on 26 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The event scripts in Automatic Bug Reporting Tool (ABRT) uses world-readable permission on a copy of sosreport file in problem directories, which allows local users to obtain sensitive information from /var/log/messages via unspecified vectors.

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

## Which versions are affected by CVE-2015-1870?

It affects 1 product.


Products: Redhat Automatic Bug Reporting Tool.

## How do I fix CVE-2015-1870?

Apply the vendor's patch.

## Is CVE-2015-1870 being exploited?

There is no known exploitation of CVE-2015-1870 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-2015-1870 and fix it if it is affected.

What it is: CVE-2015-1870 is a medium-severity vulnerability in n/a, published on 26 Jun 2017. 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-2015-1870 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-2015-1870/ (Markdown: https://insights.sbomify.com/CVE-2015-1870/index.md)
```

## Sources

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

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