# CVE-2018-10875: Ansible Arbitrary Code Execution

> Attackers can execute arbitrary code by manipulating the current working directory to load malicious Ansible plugins or modules.

- **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:** 13 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-10875, DEBIAN-CVE-2018-10875, GHSA-fc4h-467w-46rh, PYSEC-2018-43, UBUNTU-CVE-2018-10875

## What is CVE-2018-10875?

CVE-2018-10875 is a high-severity code injection vulnerability in Canonical Ubuntu Linux, published on 13 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in ansible. ansible.cfg is read from the current working directory which can be altered to make it point to a plugin or a module path under the control of an attacker, thus allowing the attacker to execute arbitrary code.

Weakness: CWE-426 (Untrusted Search Path)

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

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


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

Products: Canonical Ubuntu Linux, Debian Debian Linux, Redhat Ansible Engine, Redhat Ceph Storage, Redhat Gluster Storage, Redhat Openshift, Redhat Openstack, Redhat Virtualization, Redhat Virtualization Host, Suse Package Hub.

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

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

## Is CVE-2018-10875 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-10875 is a high-severity code injection vulnerability in Canonical Ubuntu Linux, published on 13 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-10875 in the wild and no public exploit code.

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

## Sources

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

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