# CVE-2015-5302: Information disclosure in n/a > Remote attackers can obtain sensitive crash report information due to improper file saving logic in libreport, affecting Red Hat systems. - **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Dec 2015 - **Updated:** 6 Aug 2024 - **Also known as:** GHSA-mvfv-hmwr-6c9m, RHSA-2015:2504 ## What is CVE-2015-5302? CVE-2015-5302 is a medium-severity vulnerability in n/a, published on 7 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description libreport 2.0.7 before 2.6.3 only saves changes to the first file when editing a crash report, which allows remote attackers to obtain sensitive information via unspecified vectors related to the (1) backtrace, (2) cmdline, (3) environ, (4) open_fds, (5) maps, (6) smaps, (7) hostname, (8) remote, (9) ks.cfg, or (10) anaconda-tb file attachment included in a Red Hat Bugzilla bug report. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2015-5302? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libreport` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-cli` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-compat` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-filesystem` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-gtk` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-gtk-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-newt` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-bugzilla` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-kerneloops` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-logger` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-mailx` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-reportuploader` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-rhtsupport` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-ureport` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport-python` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.9-25.el6_7 | | `libreport` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-cli` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-compat` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-filesystem` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-gtk` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-gtk-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-newt` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-bugzilla` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-kerneloops` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-logger` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-mailx` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-reportuploader` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-rhtsupport` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-plugin-ureport` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport-python` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.9-25.el6_7 | | `libreport` | Red Hat:enterprise_linux:6::server | All versions | 0:2.0.9-25.el6_7 | | `libreport-cli` | Red Hat:enterprise_linux:6::server | All versions | 0:2.0.9-25.el6_7 | | `libreport-compat` | Red Hat:enterprise_linux:6::server | All versions | 0:2.0.9-25.el6_7 | | `libreport-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.0.9-25.el6_7 | | `libreport-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.0.9-25.el6_7 | | `libreport-filesystem` | Red Hat:enterprise_linux:6::server | All versions | 0:2.0.9-25.el6_7 | Products: Redhat Libreport. ## How do I fix CVE-2015-5302? Upgrade to a fixed version. ## Is CVE-2015-5302 being exploited? There is no known exploitation of CVE-2015-5302 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2015-5302 and fix it if it is affected. What it is: CVE-2015-5302 is a medium-severity vulnerability in n/a, published on 7 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2015-5302 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-5302/ (Markdown: https://insights.sbomify.com/CVE-2015-5302/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2015-5302 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-5302 - OSV: https://osv.dev/vulnerability/CVE-2015-5302 --- From sbomify Insights: https://insights.sbomify.com/CVE-2015-5302/ Summaries are generated and may contain mistakes; the official description above is the record.