Exploited vulnerabilities · Cacti
CVE-2022-46169
Cacti Command Injection Vulnerability
Cacti contains a command injection vulnerability that allows an unauthenticated user to execute code.
Description in the NVD
Cacti is an open source platform which provides a robust and extensible operational monitoring and fault management framework for users. In affected versions a command injection vulnerability allows an unauthenticated user to execute arbitrary code on a server running Cacti, if a specific data source was selected for any monitored device. The vulnerability resides in the `remote_agent.php` file. This file can be accessed without authentication. This function retrieves the IP address of the client via `get_client_addr` and resolves this IP address to the corresponding hostname via `gethostbyaddr`. After this, it is verified that an entry within the `poller` table exists, where the hostname corresponds to the resolved hostname. If such an entry was found, the function returns `true` and the client is authorized. This authorization can be bypassed due to the implementation of the `get_client_addr` function. The function is defined in the file `lib/functions.php` and checks serval `$_SERVER` variables to determine the IP address of the client. The variables beginning with `HTTP_` can be arbitrarily set by an attacker. Since there is a default entry in the `poller` table with the hostname of the server running Cacti, an attacker can bypass the authentication e.g. by providing the header `Forwarded-For: <TARGETIP>`. This way the function `get_client_addr` returns the IP address of the server running Cacti. The following call to `gethostbyaddr` will resolve this IP address to the hostname of the server, which will pass the `poller` hostname check because of the default entry. After the authorization of the `remote_agent.php` file is bypassed, an attacker can trigger different actions. One of these actions is called `polldata`. The called function `poll_for_data` retrieves a fe
Required action according to CISA
Apply updates per vendor instructions.
What to do now
- Check your exposureFind out whether Cacti Cacti runs anywhere in your environment, including systems of suppliers.
- Patch or mitigateApply the vendor update. If that is not possible at once, use the vendor's mitigation or take the system off the network.
- Look for signs of an attackThis vulnerability is exploited in real attacks. Review the logs of affected systems for the time before the patch.
References
- github.com/Cacti/cacti/commit/7f0e16312dd5ce20f93744ef8b9c3b0f1ece2216
- github.com/Cacti/cacti/commit/a8d59e8fa5f0054aa9c6981b1cbe30ef0e2a0ec9
- github.com/Cacti/cacti/commit/b43f13ae7f1e6bfe4e8e56a80a7cd867cf2db52b
- github.com/Cacti/cacti/security/advisories/GHSA-6p93-p743-35gf
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-46169
- nvd.nist.gov/vuln/detail/CVE-2022-46169
Data: CISA Known Exploited Vulnerabilities Catalog and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.