WAF rule SQL injection

[kumar_ankush_in_bosch_com]

My Confluence search engine is working. Whenever user is try to search it automatically change to logout screen.

After checking the root cause, This is happening beacuse of the WAF rule configured for SQL injection is blocking this particular request. SQL injection is also important for us.

We have hosted our application on AWS servers and WAF is also provided by AWS only.

Is there any workaround, Which we can perform on AWS WAF rule or application side to solve this issue.

[Nic Brough -Adaptavist- · Accepted solution]

The short and brutal answer to this is that your WAF rule is inadequate.

Confluence searches are done in CQL (well, the "advanced" ones anyway), which does look a bit like SQL, so I understand the failings of the more primitive injection protection methods there - they're throwing false positives based on plain input instead of an understanding of what it's actually going to do.

But CQL entry (and the rest of Confluence) isn't a SQL injection vector, CQL is sanitised and totally divorced from the SQL.   All you can do is correct the WAF with something like "If Confluence, allow it" type rules.

[Emilio Campos]

Poor answer and useless. SQL is a database language used in the backend as CQL is used for Cassandra communication. SQL or CQL never should be present in an HTTP communication. What the WAF indicates is that strange language is passing through the HTTP communication, and obviously, that is not secure.

I have been analyzing the WAF-triggered rules protecting JIRA and Confluence and I have to say that I have never seen a piece of software not following basic security standards in HTTP like this.