Is CVE-2020-16846 exploited in the wild?

Yes. CVE-2020-16846 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.

How severe is CVE-2020-16846?

Critical severity, with a CVSS score of 3.1, published 6 November 2020.

Which products and versions are affected?

salt (PyPI) ECOSYSTEM:introduced=0,fixed=2015.8.10,introduced=2015.8.11,fixed=2015.8.13,introduced=2016.3.0,fixed=2016.3.4,introduced=2016.3.5,fixed=2016.3.6,introduced=2016.3.7,fixed=2016.3.8,introduced=2016.11.0,fixed=2016.11.3,introduced=2016.11.4,fixed=2016.11.6,introduced=2016.11.7,fixed=2016.11.10,introduced=2017.7.0,fixed=2017.7.4,introduced=2017.7.5,fixed=2017.7.8,introduced=2018.3.0rc1,fixed=2018.3.5,introduced=2019.2.0,fixed=2019.2.5,introduced=3000,fixed=3000.3, ECOSYSTEM:introduced=0,fixed=2015.8.13.

Is there a fix for CVE-2020-16846?

Yes. salt (PyPI): upgrade to 2015.8.13, 3000.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2020-16846 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2020-16846?

Check whether you run salt (PyPI) or Saltstack Salt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2020-16846: SaltStack Salt Command Injection in netapi ssh client

CVE-2020-16846 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2020-11-06

SaltStack Salt through version 3002 is vulnerable to shell injection via the Salt API. An unauthenticated remote attacker can execute arbitrary code by sending crafted web requests when the SSH client is enabled.

Technologies: salt (PyPI), Saltstack Salt. Vendors: PyPI, Saltstack.

Quick answers

Is CVE-2020-16846 exploited in the wild?: Yes. CVE-2020-16846 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.
How severe is CVE-2020-16846?: Critical severity, with a CVSS score of 3.1, published 6 November 2020.
Which products and versions are affected?: salt (PyPI) ECOSYSTEM:introduced=0,fixed=2015.8.10,introduced=2015.8.11,fixed=2015.8.13,introduced=2016.3.0,fixed=2016.3.4,introduced=2016.3.5,fixed=2016.3.6,introduced=2016.3.7,fixed=2016.3.8,introduced=2016.11.0,fixed=2016.11.3,introduced=2016.11.4,fixed=2016.11.6,introduced=2016.11.7,fixed=2016.11.10,introduced=2017.7.0,fixed=2017.7.4,introduced=2017.7.5,fixed=2017.7.8,introduced=2018.3.0rc1,fixed=2018.3.5,introduced=2019.2.0,fixed=2019.2.5,introduced=3000,fixed=3000.3, ECOSYSTEM:introduced=0,fixed=2015.8.13.
Is there a fix for CVE-2020-16846?: Yes. salt (PyPI): upgrade to 2015.8.13, 3000.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2020-16846 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2020-16846?: Check whether you run salt (PyPI) or Saltstack Salt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

salt (PyPI): upgrade to 2015.8.13, 3000.3 or later
```
pip install "salt>=3000.3"
```

Affected products

SaltStack Salt through 3002

Identifiers

CVE-2020-16846
GHSA-qr38-h96j-2j3w
PYSEC-2020-104

Timeline

2020-11-03: disclosed: SaltStack publicly disclosed the vulnerability.
2021-11-03: kev added: Added to CISA Known Exploited Vulnerabilities Catalog.
exploited: Reported as exploited in the wild.

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.