Information Disclosure in Automatic Bug Reporting Tool (CVE-2015-1870)
Summary
Vulnerability in Automatic Bug Reporting Tool (CVE-2015-1870). Confidential information can be exposed externally.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2015-1870 has been found in Automatic Bug Reporting Tool.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Automatic Bug Reporting Tool CVE-2015-1870" on the vendor's site.
CVE-2015-1870 (Automatic Bug Reporting Tool) — CWE-200 / CVSS v3 5.5
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in Automatic Bug Reporting Tool.
Check the vendor advisory for the affected versions of Automatic Bug Reporting Tool.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Automatic Bug Reporting Tool を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory securityfocus.com
- patch rhn.redhat.com
- patch bugzilla.redhat.com
- patch github.com
- patch github.com
- patch github.com
- web rhn.redhat.com