The production application triggered the "HTTP SQL Injection Attempt" threat alert, resulting in the

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

The production application triggered the "HTTP SQL Injection Attempt" threat alert, resulting in the

L1 Bithead

hi Team.
Our production application triggered the "HTTP SQL Injection Attempt" threat alert, mainly ID: 33338 and ID: 36056 and ID: 36239 and ID: 54608; affecting the production business; an exception has been made, how can we determine which SQL statements triggered these threat IDs; we want to fix these vulnerabilities with such information.

 

The threat capture packets on the device are as follows.

https://drive.google.com/drive/folders/190rJ8-04qr77uYMyNt5QIiL9eJaTEIEV?usp=sharing 

1 REPLY 1

L7 Applicator

Please open a case with Support.

  • 4964 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!