# CVE-2015-5233: Missing authorization in n/a > Authenticated users can read or delete reports from arbitrary hosts due to improper permission checks in Foreman. - **Severity:** Medium 4.2 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Apr 2016 - **Updated:** 6 Aug 2024 - **Also known as:** CVE-2015-5202, GHSA-m3c3-hv22-w332, RHSA-2015:2622 ## What is CVE-2015-5233? CVE-2015-5233 is a medium-severity missing authorization vulnerability in Redhat Satellite, published on 11 Apr 2016. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Foreman before 1.8.4 and 1.9.x before 1.9.1 do not properly apply view_hosts permissions, which allows (1) remote authenticated users with the view_reports permission to read reports from arbitrary hosts or (2) remote authenticated users with the destroy_reports permission to delete reports from arbitrary hosts via direct access to the (a) individual report show/delete pages or (b) APIs. Weakness: CWE-264 ## Which versions are affected by CVE-2015-5233? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `foreman` | Red Hat:satellite:6.1::el6 | All versions | 0:1.7.2.49-1.el6_6sat | | `foreman-compute` | Red Hat:satellite:6.1::el6 | All versions | 0:1.7.2.49-1.el6_6sat | | `foreman-debug` | Red Hat:satellite:6.1::el6 | All versions | 0:1.7.2.49-1.el6_6sat | | `foreman-discovery-image` | Red Hat:satellite:6.1::el6 | All versions | 1:3.0.5-3.el7sat | | `foreman-gce` | Red Hat:satellite:6.1::el6 | All versions | 0:1.7.2.49-1.el6_6sat | | `foreman-libvirt` | Red Hat:satellite:6.1::el6 | All versions | 0:1.7.2.49-1.el6_6sat | | `foreman-ovirt` | Red Hat:satellite:6.1::el6 | All versions | 0:1.7.2.49-1.el6_6sat | | `foreman-postgresql` | Red Hat:satellite:6.1::el6 | All versions | 0:1.7.2.49-1.el6_6sat | | `foreman-proxy` | Red Hat:satellite:6.1::el6 | All versions | 0:1.7.2.7-1.el6 | | `foreman-vmware` | Red Hat:satellite:6.1::el6 | All versions | 0:1.7.2.49-1.el6_6sat | | `gofer` | Red Hat:satellite:6.1::el6 | All versions | 0:2.6.8-1.el6 | | `katello-agent` | Red Hat:satellite:6.1::el6 | All versions | 0:2.2.6-1.el6 | | `katello-installer` | Red Hat:satellite:6.1::el6 | All versions | 0:2.3.22-1.el6 | | `katello-installer-base` | Red Hat:satellite:6.1::el6 | All versions | 0:2.3.22-1.el6 | | `libqpid-dispatch` | Red Hat:satellite:6.1::el6 | All versions | 0:0.4-11.el6 | | `python-gofer` | Red Hat:satellite:6.1::el6 | All versions | 0:2.6.8-1.el6 | | `python-gofer-proton` | Red Hat:satellite:6.1::el6 | All versions | 0:2.6.8-1.el6 | | `python-gofer-qpid` | Red Hat:satellite:6.1::el6 | All versions | 0:2.6.8-1.el6 | | `python-nectar` | Red Hat:satellite:6.1::el6 | All versions | 0:1.3.4-1.el6 | | `python-qpid` | Red Hat:satellite:6.1::el6 | All versions | 0:0.30-7.el6 | | `python-qpid-proton` | Red Hat:satellite:6.1::el6 | All versions | 0:0.9-11.el6 | | `qpid-dispatch` | Red Hat:satellite:6.1::el6 | All versions | 0:0.4-11.el6 | | `qpid-dispatch-debuginfo` | Red Hat:satellite:6.1::el6 | All versions | 0:0.4-11.el6 | | `qpid-dispatch-router` | Red Hat:satellite:6.1::el6 | All versions | 0:0.4-11.el6 | | `qpid-dispatch-tools` | Red Hat:satellite:6.1::el6 | All versions | 0:0.4-11.el6 | | `qpid-proton` | Red Hat:satellite:6.1::el6 | All versions | 0:0.9-11.el6 | | `qpid-proton-c` | Red Hat:satellite:6.1::el6 | All versions | 0:0.9-11.el6 | | `qpid-proton-debuginfo` | Red Hat:satellite:6.1::el6 | All versions | 0:0.9-11.el6 | | `ruby193-rubygem-foreman-redhat_access` | Red Hat:satellite:6.1::el6 | All versions | 0:0.2.4-1.el6_6sat | | `ruby193-rubygem-foreman_bootdisk` | Red Hat:satellite:6.1::el6 | All versions | 0:4.0.2.14-1.el6_6sat | | `ruby193-rubygem-foreman_discovery` | Red Hat:satellite:6.1::el6 | All versions | 0:2.0.0.23-1.el6_6sat | | `ruby193-rubygem-katello` | Red Hat:satellite:6.1::el6 | All versions | 0:2.2.0.77-1.el6_6sat | | `ruby193-rubygem-redhat_access_lib` | Red Hat:satellite:6.1::el6 | All versions | 0:0.0.6-1.el6_6sat | | `rubygem-hammer_cli_foreman_docker` | Red Hat:satellite:6.1::el6 | All versions | 0:0.0.3.10-1.el6 | | `rubygem-hammer_cli_foreman_docker-doc` | Red Hat:satellite:6.1::el6 | All versions | 0:0.0.3.10-1.el6 | | `rubygem-newt` | Red Hat:satellite:6.1::el6 | All versions | 0:0.9.6-1.el6 | | `rubygem-newt-debuginfo` | Red Hat:satellite:6.1::el6 | All versions | 0:0.9.6-1.el6 | | `rubygem-smart_proxy_discovery` | Red Hat:satellite:6.1::el6 | All versions | 0:1.0.3-2.el6 | | `rubygem-smart_proxy_discovery_image` | Red Hat:satellite:6.1::el6 | All versions | 0:1.0.5-3.el6 | | `foreman` | Red Hat:satellite:6.1::el7 | All versions | 0:1.7.2.49-1.el7sat | Products: Redhat Satellite, Theforeman Foreman. ## How do I fix CVE-2015-5233? Upgrade to a fixed version. ## Is CVE-2015-5233 being exploited? There is no known exploitation of CVE-2015-5233 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Satellite - [CVE-2024-7012](https://insights.sbomify.com/CVE-2024-7012/): Puppet-foreman: an authentication bypass vulnerability exists in foreman (critical 9.8) - [CVE-2024-7923](https://insights.sbomify.com/CVE-2024-7923/): Puppet-pulpcore: an authentication bypass vulnerability exists in pulpcore (critical 9.8) - [CVE-2026-96659](https://insights.sbomify.com/CVE-2026-96659/): Foreman: excessive permissions for viewer role on preview (critical 9.1) - [CVE-2023-0118](https://insights.sbomify.com/CVE-2023-0118/): Foreman: arbitrary code execution through templates (critical 9.1) - [CVE-2008-2369](https://insights.sbomify.com/CVE-2008-2369/): Hardcoded credentials in n/a (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2015-5233 and fix it if it is affected. What it is: CVE-2015-5233 is a medium-severity missing authorization vulnerability in Redhat Satellite, published on 11 Apr 2016. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2015-5233 in the wild and no public exploit code. Affected product: Redhat Satellite. 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-5233/ (Markdown: https://insights.sbomify.com/CVE-2015-5233/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2015-5233 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-5233 - OSV: https://osv.dev/vulnerability/CVE-2015-5233 --- From sbomify Insights: https://insights.sbomify.com/CVE-2015-5233/ Summaries are generated and may contain mistakes; the official description above is the record.