8000 Rule Exclusions for JetPack Debug at https://jptools.wordpress.com/debug/ · Issue #4039 · coreruleset/coreruleset · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Rule Exclusions for JetPack Debug at https://jptools.wordpress.com/debug/ #4039

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.

Sign up for GitHub

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

Jump to bottom
Open
Danrancan opened this issue Mar 8, 2025 · 2 comments
Open

Rule Exclusions for JetPack Debug at https://jptools.wordpress.com/debug/ #4039

Danrancan opened this issue Mar 8, 2025 · 2 comments
Labels
➕ False Positive ⏳ awaiting feedback CRS dev asked feedback

Comments

@Danrancan
Copy link
Danrancan commented Mar 8, 2025 •
edited
Loading

Description

I am running Modsecurity on a LEMP server running Ubuntu 22.04. I have it set up with a wordpress installation. I have installed the Jetpack plugin for wordpress, and when I go to the Jetpack Debug tools at https://jptools.wordpress.com/debug/ and enter my website address https://oddcake.net, I get the following error:

Debug
Communication error
We were unable to make an XML-RPC request to your website. Please make sure that XML-RPC is turned on and that Jetpack is installed, activated and connected with your WordPress.com account. If the error persists, try disconnecting and connecting Jetpack again.

So far, I have tried the following Rule Exclusions, but they don't seem to work, and I cannot figure it out:

SecRule REQUEST_URI "@streq /xmlrpc.php" \
    "id:1300,\
    phase:1,\
    pass,\
    nolog,\
    ctl:ruleRemoveById=942131,\
    ctl:ruleRemoveById=942430,\
    ctl:ruleRemoveById=932380,\
    ctl:ruleRemoveById=932240,\
    ctl:ruleRemoveById=942131"


SecRule REQUEST_URI "@streq /xmlrpc.php" \
    "id:1301,\
    phase:1,\
    pass,\
    nolog,\
    ctl:ruleRemoveTargetById=942131:ARGS:token,\
    ctl:ruleRemoveTargetById=942430:ARGS:token,\
    ctl:ruleRemoveTargetById=932380:ARGS:token,\
    ctl:ruleRemoveTargetById=932240:ARGS:token,\
    ctl:ruleRemoveTargetById=942131:ARGS:token"

SecRule REQUEST_URI "@streq /" \
    "id:1302,\
    phase:1,\
    pass,\
    nolog,\
    ctl:ruleRemoveTargetById=932240:ARGS:token,\
    ctl:ruleRemoveTargetById=942131:ARGS:token"

I am wondering if someone can help me with the proper rule exclusions to make the JetPack debug tool work. It seems it's having some issues reading the xmlrpc file. Please help?

How to reproduce the misbehavior (-> curl call)

Go to https://jptools.wordpress.com/debug/ and enter https://oddcake.net and test.

Logs

My modsecurity logs were to big to fit in github. So I have posted them on a pastebin here:
https://pastebin.com/G9TKdhAr

Your Environment

  • CRS version (e.g., v3.3.4): CRS 4.0
  • Paranoia level setting (e.g. PL1) : 2
  • ModSecurity version (e.g., 2.9.6): ngx_http_modsecurity_module_v1.0.3.so
  • Web Server and version or cloud provider / CDN (e.g., Apache httpd 2.4.54): Nginx v1.27.4 Mainline
  • Operating System and version: Ubuntu Server 22.04.5 LTS

Confirmation

[ X] I have removed any personal data (email addresses, IP addresses,
passwords, domain names) from any logs posted.
@Xhoenix
Copy link
Member
Xhoenix commented Mar 9, 2025

Hi @Danrancan, use a exclusion like this:-

SecRule REQUEST_URI "@beginsWith /xmlrpc.php" \
    "id:1300,\
    phase:1,\
    pass,\
    nolog,\
    ctl:ruleRemoveById=942131,\
    ctl:ruleRemoveById=942430,\
    ctl:ruleRemoveById=932380,\
    ctl:ruleRemoveById=932240"

@EsadCetiner EsadCetiner added the ⏳ awaiting feedback CRS dev asked feedback label Mar 21, 2025
@github-actions GitHub Actions
Copy link
Contributor

This issue has been open 30 days waiting for feedback. Remove the stale label or comment, or this will be closed in 14 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
➕ False Positive ⏳ awaiting feedback CRS dev asked feedback
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Danrancan @Xhoenix @EsadCetiner
0