• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the current Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Issue SQLmap attack detected (ID: 218500) on blank page

floh

Basic Pleskian
Server operating system version
Debian 10.13
Plesk version and microupdate number
18.0.60 Update #1
Hi,

I just created new subdomain. I didn't do anything on that page but I already get forbidden 403 code. I found out that Web Application Firewall (builtin from Plesk) threw the error:
Code:
ModSecurity: Access denied with code 403 (phase 2). Pattern match "[\\\\[\\\\]\\\\x22',()\\\\.]{10}$|\\\\b(?:union\\\\sall\\\\sselect\\\\s(?:(?:null|\\\\d+),?)+|order\\\\sby\\\\s\\\\d{1,4}|(?:and|or)\\\\s\\\\d{4}=\\\\d{4}|waitfor\\\\sdelay\\\\s'\\\\d+:\\\\d+:\\\\d+'|(?:select|and|or)\\\\s(?:(?:pg_)?sleep\\\\(\\\\d+\\\\)|\\\\d+\\\\s?=\\\\s?(?:dbms_pipe\\\\.receive_message\\\\ ..." at REQUEST_COOKIES:sbjs_current_add. [file "/etc/apache2/modsecurity.d/rules/comodo_free/22_SQL_SQLi.conf"] [line "64"] [id "218500"] [rev "18"] [msg "COMODO WAF: SQLmap attack detected
It's a blank page with a default index.html file. Should I be worried that my Plesk-instance may be infected? Or is this a know issue and I have to remove the rule 218500?

Do you also have such issue?

Best regards
Floh
 
It would be pretty strange if that ModSecurity rule triggered on a blank page. Does the default index page contain any content or is it an completely empty file?
 
Does the rule trigger when you access the page, or did you just find that in the logs? If the latter, is it a POST attempt?
 
The log excerpt shown above is just one ordinary SQL injection rule where SQL statements are attached to a URL as parameters. This cannot be triggered by simply opening index.html or index.php. No need to worry. It must be a log entry caused by an external source.
 
Back
Top