Description:
An SQL Injection has been identified in the /adm_program/modules/ecards/ecard_send.php source file of the Admidio Application. The SQL Injection results in a compromise of the application's database. The value of ecard_recipients POST parameter is being directly concatenated with the SQL query in the source code causing the SQL Injection.
The SQL Injection can be exploited by a member user, using blind condition-based, time-based, and Out of band interaction SQL Injection payloads. I successfully exploited SQL Injections by causing Time Delays. Advancing the payload, I was able to exfiltrate data from the database based on trial and error conditions and step-wise enumerating the characters of the database name. This was done as a POC of SQL Injection. An attacker could simply drop the database by providing a single payload, steal data, and potentially update the database according to their will.
Impact:
SQL injection (SQLi) vulnerabilities can have serious consequences for the security of a web application and its underlying database. Attackers can use SQLi to access sensitive data, and modify, delete, or add data to the database. SQLi can also be potentially used to perform RCE.
Remediation:
Use parameterized queries or prepared statements instead of concatenating user input directly into SQL queries. Parameterized queries ensure that user input is treated as data and not executable queries.
OR
Sanitize the input before including it in the SQL Query.
Steps to Reproduce:
- Intercept the POST request to
/adm_program/modules/ecards/ecard_send.php, which is used to send photo as greeting card.
- Change the value of
ecard_recipients%5B%5D POST parameter to 2%2bsleep(10).
- Sending the request will cause a time delay.
Proof Of Concept:
Figure 1: Code Vulnerable to SQL Injection
Figure 2: Code Vulnerable to SQL Injection
Figure 3: SQLi to trigger time delay
Figure 4: Data Exfiltration via Condition-based Time Delays
UmerAdeemCheema Reporter
Description:
An SQL Injection has been identified in the
/adm_program/modules/ecards/ecard_send.phpsource file of the Admidio Application. The SQL Injection results in a compromise of the application's database. The value ofecard_recipientsPOST parameter is being directly concatenated with the SQL query in the source code causing the SQL Injection.The SQL Injection can be exploited by a member user, using blind condition-based, time-based, and Out of band interaction SQL Injection payloads. I successfully exploited SQL Injections by causing Time Delays. Advancing the payload, I was able to exfiltrate data from the database based on trial and error conditions and step-wise enumerating the characters of the database name. This was done as a POC of SQL Injection. An attacker could simply drop the database by providing a single payload, steal data, and potentially update the database according to their will.
Impact:
SQL injection (SQLi) vulnerabilities can have serious consequences for the security of a web application and its underlying database. Attackers can use SQLi to access sensitive data, and modify, delete, or add data to the database. SQLi can also be potentially used to perform RCE.
Remediation:
Use parameterized queries or prepared statements instead of concatenating user input directly into SQL queries. Parameterized queries ensure that user input is treated as data and not executable queries.
OR
Sanitize the input before including it in the SQL Query.
Steps to Reproduce:
/adm_program/modules/ecards/ecard_send.php, which is used to send photo as greeting card.ecard_recipients%5B%5DPOST parameter to2%2bsleep(10).Proof Of Concept:
Figure 1: Code Vulnerable to SQL Injection
Figure 2: Code Vulnerable to SQL Injection
Figure 3: SQLi to trigger time delay
Figure 4: Data Exfiltration via Condition-based Time Delays