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.
Published 2020-09-02 18:15:11
Updated 2021-11-18 17:45:17
Source GitHub, Inc.
View at NVD,   CVE.org

Products affected by CVE-2020-15167

Exploit prediction scoring system (EPSS) score for CVE-2020-15167

0.15%
Probability of exploitation activity in the next 30 days EPSS Score History
~ 52 %
Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2020-15167

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
4.4
MEDIUM AV:L/AC:M/Au:N/C:P/I:P/A:P
3.4
6.4
NIST
8.6
HIGH CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
1.8
6.0
NIST
8.2
HIGH CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
1.8
5.8
GitHub, Inc.

CWE ids for CVE-2020-15167

  • The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
    Assigned by: security-advisories@github.com (Secondary)
  • The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.
    Assigned by: nvd@nist.gov (Primary)

References for CVE-2020-15167

Jump to
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!