# CVE-2020-15167: Arbitrary code execution via configuration file in Miller

> Attackers can execute arbitrary code by placing a malicious configuration file in the working directory of the Miller command-line utility.

- **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-15167, GHSA-mw2v-4q78-j2cw, UBUNTU-CVE-2020-15167, openSUSE-SU-2024:11048-1

## What is CVE-2020-15167?

CVE-2020-15167 is a high-severity code injection vulnerability in johnkerl miller, published on 2 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In Miller (command line utility) using the configuration file support introduced in version 5.9.0, it is possible for an attacker to cause Miller to run arbitrary code by placing a malicious `.mlrrc` file in the working directory. See linked GitHub Security Advisory for complete details. A fix is ready and will be released as Miller 5.9.1.

Weakness: CWE-427 (Uncontrolled Search Path Element), CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2020-15167?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `miller` | openSUSE:Tumbleweed | All versions | 5.10.2-1.3 |

Products: Johnkerl Miller.

## How do I fix CVE-2020-15167?

Upgrade to a fixed version.

## Is CVE-2020-15167 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15167 and fix it if it is affected.

What it is: CVE-2020-15167 is a high-severity code injection vulnerability in johnkerl miller, published on 2 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-15167 in the wild and no public exploit code.

Affected product: johnkerl miller. 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-2020-15167/ (Markdown: https://insights.sbomify.com/CVE-2020-15167/index.md)
```

## Sources

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

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