Summary
The Archery project contains multiple SQL injection vulnerabilities, that may allow an attacker to query the connected databases.
Product
Archery
Tested Version
v1.9.0
Details
SQL injection exists in the project due to unsafe user input being concatenated with a SQL query, that is passed to methods executing a query in a database. All identified issues exist due to the controller files in folder sql taking user input and not sanitizing it, which later is passed to execution. Since the controller methods are connected to and allows querying all the databases that are connected to Archery, then all databases making queries with concatenated input will be affected. In this way, one vulnerable endpoint allows for exploiting several databases. To exploit most of these SQL injections, knowledge of the exploited instance name that is defined in Archery, is needed.
Issue 2: Multiple SQL injections in sql_api/api_workflow.py endpoint ExecuteCheck post method (GHSL-2022-102)
User input coming from the db_name parameter value and the full_sql parameter value in the api_workflow.py ExecuteCheck post endpoint is passed to the below defined methods in given SQL engine implementations, which concatenate user input unsafely into a SQL query and afterwards pass it to the query method of each database engine for execution.
sql/engines/clickhouse.py > execute_check method passes unsafe user input into the sql/engines/clickhouse.py > get_table_engine method, which concatenates input which is passed to execution on the database in the sql/engines/clickhouse.py query method on line 130.sql/engines/goinception.py > execute_check method concatenates input which is passed to execution on the database in the sql/engines/goinception.py query method.sql/engines/oracle.py > execute_check method passes unsafe user input into the object_name_check method, which is passed to execution on the database in the sql/engines/oracle.py [query method] on line 640.
Remediation
Escape the variables accepting user input in sql_api/api_workflow.py ExecuteCheck post endpoint that is db_name and full_sql by using f.ex. MySQLdb.escape(). This solution is easier to implement and will fix the issues in all SQL engines at once. Using this solution, it would fix the both GHSL-2022-102 and GHSL-2022-103 vulnerabilities.
Impact
All of the issues may lead to Information Disclosure.
General remediation advice
To fix each of the issues, the best practice would be to escape the user input (as presented in Remediation section of each of the issues) or use prepared statements when executing SQL queries. Using placeholders in cursor.execute() will automatically escape the passed values. See Django documentation around executing custom SQL directly and Connections and cursors.
Generally, it is best to use prepared statements rather, but for Archery's codebase it would be much easier to fix the issues by escaping user input, which is sufficient protection. Please consider also escaping all other variables which accept input from the user, particularly the ones from GET or POST requests.
For more information on preventing SQL injection see SQL Injection Prevention Cheat Sheet - Primary Defenses
Credit
These issues were discovered and reported by GHSL team member @sylwia-budzynska (Sylwia Budzynska).
Disclosure Policy
This report is subject to our coordinated disclosure policy.
sylwia-budzynska Reporter
Summary
The Archery project contains multiple SQL injection vulnerabilities, that may allow an attacker to query the connected databases.
Product
Archery
Tested Version
v1.9.0
Details
SQL injection exists in the project due to unsafe user input being concatenated with a SQL query, that is passed to methods executing a query in a database. All identified issues exist due to the controller files in folder
sqltaking user input and not sanitizing it, which later is passed to execution. Since the controller methods are connected to and allows querying all the databases that are connected to Archery, then all databases making queries with concatenated input will be affected. In this way, one vulnerable endpoint allows for exploiting several databases. To exploit most of these SQL injections, knowledge of the exploited instance name that is defined in Archery, is needed.Issue 2: Multiple SQL injections in
sql_api/api_workflow.pyendpointExecuteCheckpostmethod (GHSL-2022-102)User input coming from the
db_nameparameter value and thefull_sqlparameter value in theapi_workflow.pyExecuteCheckpostendpoint is passed to the below defined methods in given SQL engine implementations, which concatenate user input unsafely into a SQL query and afterwards pass it to thequerymethod of each database engine for execution.sql/engines/clickhouse.py>execute_checkmethod passes unsafe user input into thesql/engines/clickhouse.py>get_table_enginemethod, which concatenates input which is passed to execution on the database in thesql/engines/clickhouse.pyquerymethod on line 130.sql/engines/goinception.py>execute_checkmethod concatenates input which is passed to execution on the database in thesql/engines/goinception.pyquerymethod.sql/engines/oracle.py>execute_checkmethod passes unsafe user input into theobject_name_checkmethod, which is passed to execution on the database in thesql/engines/oracle.py[querymethod] on line 640.Remediation
Escape the variables accepting user input in
sql_api/api_workflow.pyExecuteCheckpostendpoint that isdb_nameandfull_sqlby using f.ex. MySQLdb.escape(). This solution is easier to implement and will fix the issues in all SQL engines at once. Using this solution, it would fix the bothGHSL-2022-102andGHSL-2022-103vulnerabilities.Impact
All of the issues may lead to
Information Disclosure.General remediation advice
To fix each of the issues, the best practice would be to escape the user input (as presented in
Remediationsection of each of the issues) or use prepared statements when executing SQL queries. Using placeholders in cursor.execute() will automatically escape the passed values. See Django documentation around executing custom SQL directly and Connections and cursors.Generally, it is best to use prepared statements rather, but for Archery's codebase it would be much easier to fix the issues by escaping user input, which is sufficient protection. Please consider also escaping all other variables which accept input from the user, particularly the ones from GET or POST requests.
For more information on preventing SQL injection see SQL Injection Prevention Cheat Sheet - Primary Defenses
Credit
These issues were discovered and reported by GHSL team member @sylwia-budzynska (Sylwia Budzynska).
Disclosure Policy
This report is subject to our coordinated disclosure policy.