在mod_security中,发布& &quot“ Multipart/form-data”不起作用

发布于 2025-02-04 08:46:04 字数 879 浏览 2 评论 0 原文

我想否认Post& mod_security(modSecurity)中的request_body字符串条件。 但是它在“ Multipart/form-data”中失败。请帮助我...

详细信息

  • post& “ x-www-form-urlenCoded”不是问题。(拒绝)

  • “ x-www-form-urlenceded ”
  • 示例规则。

SecRule REQUEST_BODY "server" "id:1234,phase:2,t:none,deny"

> The above sample excludes POST conditions.
  • debug log(“多部分/form-data”)
??????? Multipart: Added part header "Content-Disposition" "form-data; name=\"server\""
~~~
??????? Adding request argument (BODY): name "server", value "sample"
~~~
Starting phase REQUEST_BODY.

~~~
??????? SecRule REQUEST_BODY "@rx server" "id:1234,phase:2,t:none,deny"
??????? Rule returned 0. ---- Not found.
  • mod_security版本:版本2系列。

  • 我尝试了其他许多测试。但是我不知道。

I'd like to deny by POST & REQUEST_BODY string condition in mod_security(ModSecurity).
But It is failed in "multipart/form-data". Please help me...

Details

  • POST & "x-www-form-urlencoded" is not problem.(denied)

  • Of course, "SecRequestBodyAccess" is activated in conf.

  • Example rule.

SecRule REQUEST_BODY "server" "id:1234,phase:2,t:none,deny"

> The above sample excludes POST conditions.
  • Debug log ("multipart/form-data")
??????? Multipart: Added part header "Content-Disposition" "form-data; name=\"server\""
~~~
??????? Adding request argument (BODY): name "server", value "sample"
~~~
Starting phase REQUEST_BODY.

~~~
??????? SecRule REQUEST_BODY "@rx server" "id:1234,phase:2,t:none,deny"
??????? Rule returned 0. ---- Not found.
  • mod_security version: version 2 series.

  • I tried other many tests. But I have no idea.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

少钕鈤記 2025-02-11 08:46:04

即使这是一个Modsecurity问题,而不是OWASP CRS问题,我也尝试回答并作为CRS Dev-on Duty:众所周知,在ModSecurity中

仅在UrlenCoded请求身体处理器时才可用
使用了,默认情况下会发生
检测到Application/X-WWW-Form-urlencoded内容类型。

请参阅此处:

因此,您的解决方案 args 而不是 request> request_body 是一个很好的解决方案。

Even if this is a ModSecurity question and not an OWASP CRS question, I try to answer and help as CRS dev-on-duty: It is known that in ModSecurity the REQUEST_BODY variable

is available only if the URLENCODED request body processor
was used, which will occur by default when the
application/x-www-form-urlencoded content type is detected.

See here: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual-%28v2.x%29#request_body

So your solution to test for ARGS instead of REQUEST_BODY is a good solution.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文