KRajanala131498 (Community Member) asked a question.
I am trying to execute the query in java but in vera scan it is showing SQL injection issue
Ask the Community
Get answers, share a use case, discuss your favorite features, or get input from the community.
By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
.png){kind=logo}
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Hi @KRajanala131498 (Community Member)
Veracode SAST would flag SQL injection CWE 89 when it finds that the SQL query is constructed dynamically. In most cases, the SQL query are dynamically constructed for the column values e.g. "Select * from Employee where Id = "+id, where the 'id' variable is untrusted data originating from untrusted sources. In such cases, We recommend using the Prepared Statement approach.
However, in your case, we see that table is supposed to be dynamic. which cannot be parameterized.
Kindly consider the solution explained in the below article to mitigate the risk.
https://community.veracode.com/s/article/sql-injection-mitigation-page2
Also, refer to the first part of this article here.
https://community.veracode.com/s/article/How-to-fix-CWE-89-SQL-Injection-flaws
If you still have questions I would recommend you schedule a consultation call to discuss.
You can check out this knowledge article (https://community.veracode.com/s/article/How-to-schedule-a-consultation-call) on how to schedule a consultation call with us.
Regards,
Kashif
Thanks for the documentation @Kashif, Security Consultant (Veracode inc) it helps me to understand the design