# CVE-2018-10874: Ansible Improper Input Validation vulnerability

> Attackers can execute arbitrary code by placing malicious inventory variables in the current working directory during ad-hoc command execution.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-10874, GHSA-3xvg-x47j-x75w, PYSEC-2018-81, UBUNTU-CVE-2018-10874

## What is CVE-2018-10874?

CVE-2018-10874 is a high-severity code injection vulnerability in Redhat Openstack, published on 2 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In ansible it was found that inventory variables are loaded from current working directory when running ad-hoc command which are under attacker's control, allowing to run arbitrary code as a result.

Weakness: CWE-20 (Improper Input Validation), CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2018-10874?

7 open source packages ship an affected version, including ansible. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ansible` | PyPI | All versions | 2.4.6.0, 2.5.6, 2.6.1 |
| `ansible` | PyPI | All versions | 2.4.6.0 |
| `ansible` | PyPI | All versions | 2.4.6.0 |
| `ansible` | PyPI | From 2.5 | 2.5.6 |
| `ansible` | PyPI | From 2.5 | 2.5.6 |
| `ansible` | PyPI | From 2.6 | 2.6.1 |
| `ansible` | PyPI | From 2.6 | 2.6.1 |

Products: Redhat Ansible Engine, Redhat Openstack, Redhat Virtualization, Redhat Virtualization Host.

## How do I fix CVE-2018-10874?

Upgrade ansible to a fixed version for your release line: 2.4.6.0, 2.5.6 or 2.6.1.

## Is CVE-2018-10874 being exploited?

There is no known exploitation of CVE-2018-10874 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Openstack

- [CVE-2020-1737](https://insights.sbomify.com/CVE-2020-1737/): Path Traversal in Ansible (high 7.5)
- [CVE-2020-1734](https://insights.sbomify.com/CVE-2020-1734/): OS Command Injection in ansible (high 7.4)
- [CVE-2019-14858](https://insights.sbomify.com/CVE-2019-14858/): Ansible leaks sensitive information to logs when told not to (high 7.3)
- [CVE-2020-10691](https://insights.sbomify.com/CVE-2020-10691/): Path Traversal in Ansible (medium 5.2)
- [CVE-2018-16859](https://insights.sbomify.com/CVE-2018-16859/): Ansible Logs Passwords If PowerShell ScriptBlock is Enabled (medium 4.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10874 and fix it if it is affected.

What it is: CVE-2018-10874 is a high-severity code injection vulnerability in Redhat Openstack, published on 2 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-10874 in the wild and no public exploit code.

Affected packages and fixed versions:
- ansible (PyPI): affected all versions; fixed in 2.4.6.0, 2.5.6, 2.6.1
- ansible (PyPI): affected all versions; fixed in 2.4.6.0
- ansible (PyPI): affected all versions; fixed in 2.4.6.0
- ansible (PyPI): affected from 2.5; fixed in 2.5.6
- ansible (PyPI): affected from 2.5; fixed in 2.5.6
- ansible (PyPI): affected from 2.6; fixed in 2.6.1
- ansible (PyPI): affected from 2.6; fixed in 2.6.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-10874/ (Markdown: https://insights.sbomify.com/CVE-2018-10874/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-10874
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-10874
- OSV: https://osv.dev/vulnerability/CVE-2018-10874

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-10874/
Summaries are generated and may contain mistakes; the official description above is the record.