# CVE-2018-16849: openstack-mistral Discloses the presence of arbitrary files within the filesystem > Attackers can determine the existence of arbitrary files on the executor filesystem by manipulating SSH private key filenames in OpenStack Mistral. - **Severity:** Low 3.1 (`CVSS:3.0/AV:N/AC:H/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:** 2 Nov 2018 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2018-16849, GHSA-fqw7-c6vr-q29m, PYSEC-2018-92, RHBA-2019:0448, UBUNTU-CVE-2018-16849 ## What is CVE-2018-16849? CVE-2018-16849 is a low-severity vulnerability in [UNKNOWN] openstack-mistral, published on 2 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A flaw was found in openstack-mistral. By manipulating the SSH private key filename, the std.ssh action can be used to disclose the presence of arbitrary files within the filesystem of the executor running the action. Since std.ssh private_key_filename can take an absolute path, it can be used to assess whether or not a file exists on the executor's filesystem. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2018-16849? 3 open source packages ship an affected version, including mistral. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mistral` | PyPI | All versions | 7.0.1 | | `mistral` | PyPI | All versions | 7.0.1 | | `mistral` | PyPI | All versions | 7.0.1 | | `instack-undercloud` | Red Hat:openstack:13::el7 | All versions | 0:8.4.6-6.el7ost | | `openstack-mistral` | Red Hat:openstack:13::el7 | All versions | 0:6.0.6-2.el7ost | | `openstack-mistral-all` | Red Hat:openstack:13::el7 | All versions | 0:6.0.6-2.el7ost | | `openstack-mistral-api` | Red Hat:openstack:13::el7 | All versions | 0:6.0.6-2.el7ost | | `openstack-mistral-common` | Red Hat:openstack:13::el7 | All versions | 0:6.0.6-2.el7ost | | `openstack-mistral-engine` | Red Hat:openstack:13::el7 | All versions | 0:6.0.6-2.el7ost | | `openstack-mistral-event-engine` | Red Hat:openstack:13::el7 | All versions | 0:6.0.6-2.el7ost | | `openstack-mistral-executor` | Red Hat:openstack:13::el7 | All versions | 0:6.0.6-2.el7ost | | `openstack-tripleo-common` | Red Hat:openstack:13::el7 | All versions | 0:8.6.6-16.el7ost | | `openstack-tripleo-common-container-base` | Red Hat:openstack:13::el7 | All versions | 0:8.6.6-16.el7ost | | `openstack-tripleo-common-containers` | Red Hat:openstack:13::el7 | All versions | 0:8.6.6-16.el7ost | | `openstack-tripleo-common-devtools` | Red Hat:openstack:13::el7 | All versions | 0:8.6.6-16.el7ost | | `openstack-tripleo-heat-templates` | Red Hat:openstack:13::el7 | All versions | 0:8.2.0-6.1.el7ost | | `openstack-tripleo-image-elements` | Red Hat:openstack:13::el7 | All versions | 0:8.0.1-3.el7ost | | `openstack-tripleo-puppet-elements` | Red Hat:openstack:13::el7 | All versions | 0:8.0.1-2.el7ost | | `openstack-tripleo-ui` | Red Hat:openstack:13::el7 | All versions | 0:8.3.2-3.el7ost | | `openstack-tripleo-validations` | Red Hat:openstack:13::el7 | All versions | 0:8.4.4-2.el7ost | | `os-net-config` | Red Hat:openstack:13::el7 | All versions | 0:8.4.3-6.el7ost | | `os-refresh-config` | Red Hat:openstack:13::el7 | All versions | 0:8.3.1-0.20180918214345.4703b54.el7ost | | `puppet-cinder` | Red Hat:openstack:13::el7 | All versions | 0:12.4.1-3.el7ost | | `puppet-keystone` | Red Hat:openstack:13::el7 | All versions | 0:12.4.0-4.el7ost | | `puppet-manila` | Red Hat:openstack:13::el7 | All versions | 0:12.5.0-3.el7ost | | `puppet-neutron` | Red Hat:openstack:13::el7 | All versions | 0:12.4.1-4.ed05e01git.el7ost | | `puppet-nova` | Red Hat:openstack:13::el7 | All versions | 0:12.4.0-16.el7ost | | `puppet-octavia` | Red Hat:openstack:13::el7 | All versions | 0:12.4.0-8.el7ost | | `puppet-opendaylight` | Red Hat:openstack:13::el7 | All versions | 0:8.2.2-5.9126c8dgit.el7ost | | `puppet-ovn` | Red Hat:openstack:13::el7 | All versions | 0:12.4.0-2.el7ost | | `puppet-pacemaker` | Red Hat:openstack:13::el7 | All versions | 0:0.7.2-0.20180423212257.el7ost | | `puppet-swift` | Red Hat:openstack:13::el7 | All versions | 0:12.4.0-4.el7ost | | `puppet-tripleo` | Red Hat:openstack:13::el7 | All versions | 0:8.3.6-15.el7ost | | `python-mistral` | Red Hat:openstack:13::el7 | All versions | 0:6.0.6-2.el7ost | | `python-mistral-tests` | Red Hat:openstack:13::el7 | All versions | 0:6.0.6-2.el7ost | | `python-os-brick` | Red Hat:openstack:13::el7 | All versions | 0:2.3.4-2.el7ost | | `python-tripleoclient` | Red Hat:openstack:13::el7 | All versions | 0:9.2.6-8.el7ost | | `python2-os-brick` | Red Hat:openstack:13::el7 | All versions | 0:2.3.4-2.el7ost | Products: Redhat Openstack-Mistral. ## How do I fix CVE-2018-16849? Upgrade mistral to 7.0.1 or later. ## Is CVE-2018-16849 being exploited? There is no known exploitation of CVE-2018-16849 in the wild and no public exploit code. ## Other vulnerabilities in [UNKNOWN] openstack-mistral - [CVE-2018-16848](https://insights.sbomify.com/CVE-2018-16848/): OpenStack Mistral DoS (medium 6.5) - [CVE-2019-3866](https://insights.sbomify.com/CVE-2019-3866/): Information disclosure in openstack-mistral (medium 5.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-16849 and fix it if it is affected. What it is: CVE-2018-16849 is a low-severity vulnerability in [UNKNOWN] openstack-mistral, published on 2 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2018-16849 in the wild and no public exploit code. Affected packages and fixed versions: - mistral (PyPI): affected all versions; fixed in 7.0.1 - mistral (PyPI): affected all versions; fixed in 7.0.1 - mistral (PyPI): affected all versions; fixed in 7.0.1 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-2018-16849/ (Markdown: https://insights.sbomify.com/CVE-2018-16849/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-16849 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-16849 - OSV: https://osv.dev/vulnerability/CVE-2018-16849 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-16849/ Summaries are generated and may contain mistakes; the official description above is the record.