# CVE-2019-10159: Missing authorization in cfme > An unprivileged user can access all VM migration logs due to improper authorization in the migration log controller. - **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 14 Jun 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-whhr-m9m3-wj45, RHSA-2019:2466 ## What is CVE-2019-10159? CVE-2019-10159 is a medium-severity missing authorization vulnerability in Red Hat cfme, published on 14 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description cfme-gemset versions 5.10.4.3 and below, 5.9.9.3 and below are vulnerable to a data leak, due to an improper authorization in the migration log controller. An attacker with access to an unprivileged user can access all VM migration logs available. Weakness: CWE-285 (Improper Authorization) ## Which versions are affected by CVE-2019-10159? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ansible-tower` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:3.5.1-1.el7at | | `ansible-tower-server` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:3.5.1-1.el7at | | `ansible-tower-setup` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:3.5.1-1.el7at | | `ansible-tower-ui` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:3.5.1-1.el7at | | `ansible-tower-venv-ansible` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:3.5.1-1.el7at | | `ansible-tower-venv-tower` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:3.5.1-1.el7at | | `cfme` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:5.10.8.0-1.el7cf | | `cfme-amazon-smartstate` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:5.10.8.0-1.el7cf | | `cfme-appliance` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:5.10.8.0-1.el7cf | | `cfme-appliance-common` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:5.10.8.0-1.el7cf | | `cfme-appliance-debuginfo` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:5.10.8.0-1.el7cf | | `cfme-appliance-tools` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:5.10.8.0-1.el7cf | | `cfme-debuginfo` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:5.10.8.0-1.el7cf | | `cfme-gemset` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:5.10.8.0-1.el7cf | | `cfme-gemset-debuginfo` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:5.10.8.0-1.el7cf | | `rubygem-nokogiri` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:1.8.5-1.el7cf | | `rubygem-nokogiri-debuginfo` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:1.8.5-1.el7cf | | `rubygem-nokogiri-doc` | Red Hat:cloudforms_managementengine:5.10::el7 | All versions | 0:1.8.5-1.el7cf | Products: Redhat Cfme-Gemset, Redhat Cloudforms. ## How do I fix CVE-2019-10159? Apply the vendor's patch. ## Is CVE-2019-10159 being exploited? There is no known exploitation of CVE-2019-10159 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-10159 and fix it if it is affected. What it is: CVE-2019-10159 is a medium-severity missing authorization vulnerability in Red Hat cfme, published on 14 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-10159 in the wild and no public exploit code. Affected product: Red Hat cfme. 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-2019-10159/ (Markdown: https://insights.sbomify.com/CVE-2019-10159/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10159 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10159 - OSV: https://osv.dev/vulnerability/CVE-2019-10159 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-10159/ Summaries are generated and may contain mistakes; the official description above is the record.