Skip to content
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

is sanitiseArgs not supported in libmodsecurity3 version 3.0.12 #3140

Closed
an1ruddh opened this issue May 12, 2024 · 5 comments
Closed

is sanitiseArgs not supported in libmodsecurity3 version 3.0.12 #3140

an1ruddh opened this issue May 12, 2024 · 5 comments
Labels
3.x Related to ModSecurity version 3.x

Comments

@an1ruddh
Copy link

an1ruddh commented May 12, 2024

No description provided.

@an1ruddh an1ruddh added the 3.x Related to ModSecurity version 3.x label May 12, 2024
@airween
Copy link
Member

airween commented May 12, 2024

Hi @an1ruddh,

sorry for the question, but are you asking this or are you reporting a known issue?

@an1ruddh
Copy link
Author

i am actually asking sorry I just checked it's still in TBI

@tiptop-crazy
Copy link

Hi @an1ruddh @airween ,

  1. Maybe there are other options for solving the problem, dispite sanitise* is not implemented in v3 ? For istance, can I somehow set MATCHED_VAR to ******** if MATCHED_VAR_NAME is password in
    logdata:'Matched Data: %{TX.0} found within %{MATCHED_VAR_NAME}: %{MATCHED_VAR}'
    Can I somehow use Lua for it?

  2. And If it is possible, how can I apply this to all rules without modifying each one individually ?

@airween
Copy link
Member

airween commented May 15, 2024

i am actually asking sorry I just checked it's still in TBI

Right, thanks - feel free to close the issue if you don't have any other question.

@airween
Copy link
Member

airween commented May 15, 2024

1. Maybe there are other options for solving the problem, dispite sanitise* is not implemented in v3 ? For istance, can I somehow  set _MATCHED_VAR_ to ******** if _MATCHED_VAR_NAME_ is **password** in
   logdata:'Matched Data: %{TX.0} found within %{MATCHED_VAR_NAME}: %{MATCHED_VAR}'
   Can I somehow use Lua for it?

I'm not sure about that. Eg. as I know Lua extension does not support to modify logs (neither the rules)

2. And If it is possible, how can I apply this to all rules without modifying each one individually ?

I'm afraid while it's not possible therefore this question is not relevant.

The solution is to implement these actions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.x Related to ModSecurity version 3.x
Projects
None yet
Development

No branches or pull requests

3 participants