Saturday, March 29, 2025
HomeCVE/vulnerabilityAppsmith Developer Tool Vulnerability Exposes Systems to Remote Code Execution

Appsmith Developer Tool Vulnerability Exposes Systems to Remote Code Execution

Published on

SIEM as a Service

Follow Us on Google News

A recent analysis by Rhino Security Labs has uncovered a series of critical vulnerabilities in the Appsmith developer tool, a platform used for building internal applications such as dashboards and customer support tools.

The most severe of these vulnerabilities is CVE-2024-55963, which enables unauthenticated remote code execution due to a misconfigured PostgreSQL database that ships with the product.

Appsmith, an open-source developer tool, is popular for its ability to connect various data sources to user interfaces, including databases and Large Language Models (LLMs).

However, the default installation includes a misconfigured PostgreSQL database.

This configuration allows any local user to connect as any PostgreSQL user
This configuration allows any local user to connect as any PostgreSQL user

Specifically, the PostgreSQL authentication file (pg_hba.conf) is set to allow any local user to connect as any PostgreSQL user without a password, which can be exploited for remote code execution.

The exploitation path leverages Appsmith’s default configuration that allows user signup. An attacker can sign up for the application, create a new workspace and application, and connect to the vulnerable PostgreSQL database.

From there, they can execute SQL queries that enable system command execution, posing a significant risk to any organization relying on Appsmith.

Proof of Concept Explained

A proof-of-concept exploit demonstrates how attackers can abuse this vulnerability. It involves creating a table, copying data from a program into the table (e.g., cat /etc/passwd), selecting data from the table, and then dropping the table to clean up tracks.

This image shows the connection request using any arbitrary value for the Postgres User.
This image shows the connection request using any arbitrary value for the Postgres User.
This image shows the successful response connecting to the postgresql database with an arbitrary value for the password
This image shows the successful response connecting to the postgresql database with an arbitrary value for the password

This exploitability is facilitated by the application server connecting to the database directly, allowing attackers to bypass client-side security checks.

CREATE TABLE PoC (column1 TEXT);

COPY PoC FROM PROGRAM 'cat /etc/passwd';

SELECT * FROM PoC;

DROP PoC; -- Cleans up the database after the exploit

Additional Vulnerabilities

Beyond CVE-2024-55963, two other vulnerabilities have been identified:

CVE-2024-55964: Insecure Direct Object Reference (IDOR) Allowing Unauthorized SQL Access

This vulnerability affects users with the “App Viewer” role, who are only supposed to have view-only permissions.

However, through API manipulation, attackers can identify and access database connections, allowing them to execute arbitrary SQL queries against databases within accessible workspaces.

The exploit relies on brute-forcing predictable parts of the datasource IDs and using specific API endpoints designed for SQL databases.

Though this vulnerability is mitigated by workspace-level authorization, it still poses a risk for sensitive data exposure.

CVE-2024-55965: Denial of Service via Broken Access Control

This vulnerability involves a flawed permission check that allows “App Viewer” users to restart the application server, triggering a denial-of-service attack.

Exploited by leveraging persistent session cookies, attackers can automate repeated restart requests, temporarily disabling access to the application.

The flaw lies in the Global Exception Handler, which improperly bypasses permission checks for certain requests, including the restart function. This leads to unauthorized access to administrative-level operations.

Impact and Mitigation

These vulnerabilities impact Appsmith versions 1.20 through 1.51 across their product lineup. To mitigate these risks, organizations are advised to update their Appsmith installations to versions that include patches for these vulnerabilities.

Rhino Security Labs has provided detailed exploit scripts and detection tools to help security teams identify and protect against these vulnerabilities.

The scripts and tools are available in their CVE Github repository, offering proactive measures to safeguard against potential attacks.

The revelations of these critical vulnerabilities highlight the importance of rigorous security testing and configuration audits in software development tools.

Organizations utilizing Appsmith should prioritize updating their installations and reviewing their current setups to prevent unauthorized access and potential remote code execution.

By acting promptly, companies can protect their systems and data from these vulnerabilities, ensuring the continued use of Appsmith’s beneficial functionalities while minimizing risk exposure.

Are you from SOC/DFIR Teams? – Analyse Malware, Phishing Incidents & get live Access with ANY.RUN -> Start Now for Free. 

Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

Gamaredon Hackers Weaponize LNK Files to Deliver Remcos Backdoor

Cisco Talos has uncovered an ongoing cyber campaign by the Gamaredon threat actor group,...

“Crocodilus” A New Malware Targeting Android Devices for Full Takeover

Researchers have uncovered a dangerous new mobile banking Trojan dubbed Crocodilus actively targeting financial...

SquareX Discloses Browser-Native Ransomware that Puts Millions at Risk

From WannaCry to the MGM Resorts Hack, ransomware remains one of the most damaging...

Hackers Exploit DNS MX Records to Create Fake Logins Imitating 100+ Brands

Cybersecurity researchers have discovered a sophisticated phishing-as-a-service (PhaaS) platform, dubbed "Morphing Meerkat," that leverages...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Gamaredon Hackers Weaponize LNK Files to Deliver Remcos Backdoor

Cisco Talos has uncovered an ongoing cyber campaign by the Gamaredon threat actor group,...

“Crocodilus” A New Malware Targeting Android Devices for Full Takeover

Researchers have uncovered a dangerous new mobile banking Trojan dubbed Crocodilus actively targeting financial...

Hackers Exploit DNS MX Records to Create Fake Logins Imitating 100+ Brands

Cybersecurity researchers have discovered a sophisticated phishing-as-a-service (PhaaS) platform, dubbed "Morphing Meerkat," that leverages...