-
-
Notifications
You must be signed in to change notification settings - Fork 402
Modsecurity with Passwordstate #1923
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
Yes, |
Is there any specifics of what I should be asking of the application vendor? They were upfront and told me that it is an ASP.NET application which I see commonly uses .axd extensions. |
Ok. You can remove this extension from restricted in configuration file
|
Thanks @azurit, that seems to have resolved that issue. However I now have another one related to rule 954120 - IIS Information Leakage. Should I raise this as a new issue? |
Yes, thank you. |
Description
When Modsecurity is enabled in my virtual hosts file, authentication into the application fails. It is supposed to authenticate with AD, then complete an OTP challenge. Even with the OTP challenge disabled, the AD authentication doesn't seem to happen - i.e. login credentials go blank, like the page is reset.
The backend IIS server does not seem to have anything to suggest that a login was even attempted.
Application is PasswordState - https://www.clickstudios.com.au/
Audit Logs / Triggered Rule Numbers
Virtual Host access.log
Your Environment
Comments
A brief search led me to believe that this may be getting blocked because of a rule not allowing .axd extension - is my assumption here correct?
If so, is there a safe way to ignore it?
Confirmation
[ X ] I have removed any personal data (email addresses, IP addresses,
passwords, domain names) from any logs posted.
The text was updated successfully, but these errors were encountered: