-
Notifications
You must be signed in to change notification settings - Fork 1.7k
issue with MULTIPART_UNMATCHED_BOUNDARY [id "200003"] v2.9.2 #1804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Related to #1747 |
hi and by comment rule i can upload: |
Hi MohsenNa, do you have ModSecurity 2.9? If yes, please review all of this thread, especially this comment. If you have 3.0 branch, please upgrade to the current master branch, and see the solution: Anyway, the size of uploaded content not affects this issue, but if you have any boundary-like line in content, the it does. |
yes my version is 3.0 |
Can someone tell me if this issue is related to this error? This is on fedora28 with mod_security-2.9.2-5.fc28.x86_64 [Fri Feb 08 22:06:50.144344 2019] [:error] [pid 11255:tid 140146947102464] [client 151.106.0.210:54982] [client 151.106.0.210] ModSecurity: Access denied with code 403 (phase 2). Match of "eq 0" against "MULTIPART_UNMATCHED_BOUNDARY" required. [file "/etc/httpd/conf.d/mod_security.conf"] [line "35"] [id "200003"] [msg "Multipart parser detected a possible unmatched boundary."] [hostname "linuxsecurity.com"] [uri "/index.php"] [unique_id "XF5Dyf3kxTYC2M5TGQgxsAAAANU"], referer: https://linuxsecurity.com/index.php?option=com_content&task=new§ionid=9&itemid=0 |
I get with upload a image this error:
like #652
I upload simple with
<form action="myupload" method="post" accept-charset="utf-8" enctype="multipart/form-data"><input type="file" name="image"><button type="submit" name="submit">Upload</button></form>
one of many many many image-files with this error "--"
I use modsecurity2.9.2-1.el7 and its set as "off". So why its catch this issue?
System: CentOS Linux 7.5.1804 (Core) with Product Plesk Onyx Version 17.5.3
etc/httpd/conf.d/mod_security.conf
The text was updated successfully, but these errors were encountered: