# CVE-2017-16239: OpenStack Nova Filter Scheduler Bypass > Authenticated users can bypass scheduler filters by rebuilding instances, potentially violating isolation policies in OpenStack Nova deployments. - **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Nov 2017 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2017-16239, DSA-4056-1, GHSA-w2wf-cgwh-vpqg, PYSEC-2026-694, RHSA-2018:0241, RHSA-2018:0314, RHSA-2018:0369, SUSE-SU-2017:3080-1, UBUNTU-CVE-2017-16239 ## What is CVE-2017-16239? CVE-2017-16239 is a medium-severity vulnerability in n/a, published on 14 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description In OpenStack Nova through 14.0.9, 15.x through 15.0.7, and 16.x through 16.0.2, by rebuilding an instance, an authenticated user may be able to circumvent the Filter Scheduler bypassing imposed filters (for example, the ImagePropertiesFilter or the IsolatedHostsFilter). All setups using Nova Filter Scheduler are affected. Because of the regression described in Launchpad Bug #1732947, the preferred fix is a 14.x version after 14.0.10, a 15.x version after 15.0.8, or a 16.x version after 16.0.3. ## Which versions are affected by CVE-2017-16239? 7 open source packages ship an affected version, including nova. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `nova` | PyPI | From 14.0.0 | 14.0.10, 15.0.8, 16.0.3 | | `nova` | PyPI | From 14.0.0 | 14.0.10 | | `nova` | PyPI | From 14.0.0 | 14.0.10 | | `nova` | PyPI | From 15.0.0 | 15.0.8 | | `nova` | PyPI | From 15.0.0 | 15.0.8 | | `nova` | PyPI | From 16.0.0 | 16.0.3 | | `nova` | PyPI | From 16.0.0 | 16.0.3 | | `openstack-nova` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-api` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-cells` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-cert` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-common` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-compute` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-conductor` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-console` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-migration` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-network` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-novncproxy` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-placement-api` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-scheduler` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-serialproxy` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `openstack-nova-spicehtml5proxy` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `python-nova` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `python-nova-tests` | Red Hat:openstack:10::el7 | All versions | 1:14.1.0-3.el7ost | | `python-novaclient` | Red Hat:openstack:10::el7 | All versions | 1:6.0.2-2.el7ost | | `openstack-nova` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-api` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-cells` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-cert` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-common` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-compute` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-conductor` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-console` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-migration` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-network` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-novncproxy` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-placement-api` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-scheduler` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-serialproxy` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | | `openstack-nova-spicehtml5proxy` | Red Hat:openstack:11::el7 | All versions | 1:15.0.8-5.el7ost | Products: Openstack Nova. ## How do I fix CVE-2017-16239? Upgrade nova to a fixed version for your release line: 14.0.10, 15.0.8 or 16.0.3. ## Is CVE-2017-16239 being exploited? There is no known exploitation of CVE-2017-16239 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2017-7214](https://insights.sbomify.com/CVE-2017-7214/): OpenStack Nova logs sensitive context from notification exceptions (critical 9.8) - [CVE-2017-17051](https://insights.sbomify.com/CVE-2017-17051/): OpenStack Nova DoS by rebuilding the same instance with a new image multiple times (high 8.6) - [CVE-2020-17376](https://insights.sbomify.com/CVE-2020-17376/): OpenStack Nova Live migration fails to update persistent domain XML (high 8.3) - [CVE-2017-18191](https://insights.sbomify.com/CVE-2017-18191/): OpenStack Nova Denial of service attack on the compute host (high 7.5) - [CVE-2015-3280](https://insights.sbomify.com/CVE-2015-3280/): OpenStack Compute (nova) allows remote authenticated users to cause a denial of service (medium 6.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-16239 and fix it if it is affected. What it is: CVE-2017-16239 is a medium-severity vulnerability in n/a, published on 14 Nov 2017. 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-16239 in the wild and no public exploit code. Affected packages and fixed versions: - nova (PyPI): affected from 14.0.0; fixed in 14.0.10, 15.0.8, 16.0.3 - nova (PyPI): affected from 14.0.0; fixed in 14.0.10 - nova (PyPI): affected from 14.0.0; fixed in 14.0.10 - nova (PyPI): affected from 15.0.0; fixed in 15.0.8 - nova (PyPI): affected from 15.0.0; fixed in 15.0.8 - nova (PyPI): affected from 16.0.0; fixed in 16.0.3 - nova (PyPI): affected from 16.0.0; fixed in 16.0.3 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-16239/ (Markdown: https://insights.sbomify.com/CVE-2017-16239/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-16239 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-16239 - OSV: https://osv.dev/vulnerability/CVE-2017-16239 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-16239/ Summaries are generated and may contain mistakes; the official description above is the record.