# CVE-2017-7510: Information disclosure in RHV > Attackers can retrieve root passwords via the REST interface if cloud-init is used, leading to potential host compromise. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **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:** 25 Mar 2019 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-4mqp-w6v5-gr6x, RHEA-2017:1814 ## What is CVE-2017-7510? CVE-2017-7510 is a high-severity vulnerability in [UNKNOWN] RHV, published on 25 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description In ovirt-engine 4.1, if a host was provisioned with cloud-init, the root password could be revealed through the REST interface. Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2017-7510? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ovirt-engine` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-backend` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-dbscripts` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-extensions-api-impl` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-extensions-api-impl-javadoc` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-lib` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-restapi` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-setup` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-setup-base` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-setup-plugin-ovirt-engine` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-setup-plugin-ovirt-engine-common` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-setup-plugin-vmconsole-proxy-helper` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-setup-plugin-websocket-proxy` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-tools` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-tools-backup` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-userportal` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-vmconsole-proxy-helper` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-webadmin-portal` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `ovirt-engine-websocket-proxy` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | | `rhevm` | Red Hat:rhev_manager:4 | All versions | 0:4.1.4.2-0.1.el7 | Products: Redhat Ovirt-Engine. ## How do I fix CVE-2017-7510? Apply the vendor's patch. ## Is CVE-2017-7510 being exploited? There is no known exploitation of CVE-2017-7510 in the wild and no public exploit code. ## Other vulnerabilities in [UNKNOWN] RHV - [CVE-2014-0151](https://insights.sbomify.com/CVE-2014-0151/): Cross-site request forgery in n/a (medium 6.8) - [CVE-2015-1780](https://insights.sbomify.com/CVE-2015-1780/): Missing authorization in oVirt (medium 6.5) - [CVE-2016-3077](https://insights.sbomify.com/CVE-2016-3077/): Denial of service in n/a (medium 6.5) - [CVE-2016-3113](https://insights.sbomify.com/CVE-2016-3113/): Cross-site scripting in n/a (medium 6.1) - [CVE-2018-1062](https://insights.sbomify.com/CVE-2018-1062/): Information disclosure in oVirt (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-7510 and fix it if it is affected. What it is: CVE-2017-7510 is a high-severity vulnerability in [UNKNOWN] RHV, published on 25 Mar 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-2017-7510 in the wild and no public exploit code. Affected product: [UNKNOWN] RHV. 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-2017-7510/ (Markdown: https://insights.sbomify.com/CVE-2017-7510/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7510 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7510 - OSV: https://osv.dev/vulnerability/CVE-2017-7510 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-7510/ Summaries are generated and may contain mistakes; the official description above is the record.