CVE Vulnerabilities

CVE-2024-22197

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

Published: Jan 11, 2024 | Modified: Feb 29, 2024
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

Nginx-ui is online statistics for Server Indicators​​ Monitor CPU usage, memory usage, load average, and disk usage in real-time. The Home > Preference page exposes a small list of nginx settings such as Nginx Access Log Path and Nginx Error Log Path. However, the API also exposes test_config_cmd, reload_cmd and restart_cmd. While the UI doesnt allow users to modify any of these settings, it is possible to do so by sending a request to the API. This issue may lead to authenticated Remote Code Execution, Privilege Escalation, and Information Disclosure. This issue has been patched in version 2.0.0.beta.9.

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
Nginx_ui Nginxui * *
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0
Nginx_ui Nginxui 2.0.0 2.0.0

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