ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
SQL injection protection on Perform JDBC Query assertion
Article ID: 142965
Updated On:
Products
CA API Gateway
API SECURITY
CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7)
CA API Gateway Enterprise Service Manager (Layer 7)
STARTER PACK-7
CA Microgateway
Issue/Introduction
Can you give any information on whether there is any build-in SQL injection protection on the "JDBC Query assertion"?
The documentation does not say anything about this.
For example: We are using queries like this (without the "Convert Variables to Strings" option checked): INSERT INTO SomeTable (Somecolumn) VALUES (${someValue});
Is such usage at risk for sql injection attacks or will the api gateway execute this using prepared statements?
Environment
Release : 9.4
Component : API GTW ENTERPRISE MANAGER
Resolution
Gateway uses prepared statements and replaces the context variable references with the parameter marker (?).
Option "Convert Variables to Strings" ensures you to supply the value to the parameter as String or as it is.
Imagine, multi-value context variable is referenced, its value is stringified as a comma-separated list. In such cases, you might require to pass the values as it is.
Otherwise, JDBC query execution is free from SQL injection attacks.
Option "Convert Variables to Strings" ensures you to supply the value to the parameter as String or as it is.
Imagine, multi-value context variable is referenced, its value is stringified as a comma-separated list. In such cases, you might require to pass the values as it is.
Otherwise, JDBC query execution is free from SQL injection attacks.
Feedback
Yes
No
Powered by
