CVE Vulnerabilities

CVE-2021-3148

Improper Neutralization of Special Elements used in a Command ('Command Injection')

Published: Feb 27, 2021 | Modified: Dec 21, 2023
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
6.8 MODERATE
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Ubuntu
MEDIUM

An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.

Weakness

The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

Affected Software

Name Vendor Start Version End Version
Salt Saltstack * 2015.8.10 (excluding)
Salt Saltstack 2015.8.11 (including) 2015.8.13 (excluding)
Salt Saltstack 2016.3.0 (including) 2016.3.4 (excluding)
Salt Saltstack 2016.3.5 (including) 2016.3.6 (excluding)
Salt Saltstack 2016.3.7 (including) 2016.3.8 (excluding)
Salt Saltstack 2016.3.9 (including) 2016.11.3 (excluding)
Salt Saltstack 2016.11.4 (including) 2016.11.5 (excluding)
Salt Saltstack 2016.11.7 (including) 2016.11.10 (excluding)
Salt Saltstack 2017.5.0 (including) 2017.7.8 (excluding)
Salt Saltstack 2018.2.0 (including) 2018.3.5 (including)
Salt Saltstack 2019.2.0 (including) 2019.2.5 (excluding)
Salt Saltstack 2019.2.6 (including) 2019.2.8 (excluding)
Salt Saltstack 3000 (including) 3000.6 (excluding)
Salt Saltstack 3001 (including) 3001.4 (excluding)
Salt Saltstack 3002 (including) 3002.5 (excluding)
Salt Ubuntu bionic *
Salt Ubuntu esm-apps/bionic *
Salt Ubuntu groovy *
Salt Ubuntu hirsute *
Salt Ubuntu impish *
Salt Ubuntu kinetic *
Salt Ubuntu trusty *
Salt Ubuntu xenial *

Extended Description

Command injection vulnerabilities typically occur when:

Many protocols and products have their own custom command language. While OS or shell command strings are frequently discovered and targeted, developers may not realize that these other command languages might also be vulnerable to attacks. Command injection is a common problem with wrapper programs.

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

References