Netdata is an open source option for real-time infrastructure monitoring and troubleshooting. An attacker with the ability to establish a streaming connection can execute arbitrary commands on the targeted Netdata agent. When an alert is triggered, the function health_alarm_execute
is called. This function performs different checks and then enqueues a command by calling spawn_enq_cmd
. This command is populated with several arguments that are not sanitized. One of them is the registry_hostname
of the node for which the alert is raised. By providing a specially crafted registry_hostname
as part of the health data that is streamed to a Netdata (parent) agent, an attacker can execute arbitrary commands at the remote host as a side-effect of the raised alert. Note that the commands are executed as the user running the Netdata Agent. This user is usually named netdata
. The ability to run arbitrary commands may allow an attacker to escalate privileges by escalating other vulnerabilities in the system, as that user. The problem has been fixed in: Netdata agent v1.37 (stable) and Netdata agent v1.36.0-409 (nightly). As a workaround, streaming is not enabled by default. If you have previously enabled this, it can be disabled. Limiting access to the port on the recipient Agent to trusted child connections may mitigate the impact of this vulnerability.
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.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Netdata | Netdata | * | 1.37.0 (excluding) |
Netdata | Ubuntu | bionic | * |
Netdata | Ubuntu | kinetic | * |
Netdata | Ubuntu | lunar | * |
Netdata | Ubuntu | mantic | * |
Netdata | Ubuntu | trusty | * |
Netdata | Ubuntu | xenial | * |
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.