Skip to content

This version of ModSecurity was not compiled with GeoIP or MaxMind support. #1911

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

Closed
nix0x00 opened this issue Sep 22, 2018 · 5 comments
Closed
Assignees
Labels
RIP - Type - Usage Related with usage (not a bug)
Milestone

Comments

@nix0x00
Copy link

nix0x00 commented Sep 22, 2018

Hi,

I am trying to install ModSec module with Nginx and for that I need GeoIP. I have installed libmaxminddb by following tar.gz installation mentioned here: https://github.com/maxmind/libmaxminddb

And then I downloaded (https://github.com/leev/ngx_http_geoip2_module) and compiled successfully, but owasp modsecurity rules is showing me this error even though I compiled it with maxmind.

nginx: [emerg] "modsecurity_rules_file" directive Rules error. File: /usr/local/owasp-modsecurity-crs-3.0.0/rules/REQUEST-910-IP-REPUTATION.conf. Line: 69. Column: 20. This version of ModSecurity was not compiled with GeoIP or MaxMind support. in /etc/nginx/nginx.conf:62

Please tell me how can I know if libmaxminddb was installed correctly?

@victorhora victorhora self-assigned this Sep 22, 2018
@victorhora victorhora added the RIP - Type - Usage Related with usage (not a bug) label Sep 22, 2018
@victorhora victorhora modified the milestones: v2.9.3, v3.0.3 Sep 22, 2018
@victorhora
Copy link
Contributor

Which version of ModSecurity you're running? 2.9.x? 3.0.x? Notice that libMaxMind is only supported on libModSecurity (aka ModSecurity v3).

If you are running v3, make sure you have at least v3.0.2 or cloning from latest master.

If you are running 2.9.x, only GeoIP is supported (which is getting deprecated).

@nix0x00
Copy link
Author

nix0x00 commented Sep 23, 2018

Hi, I downloaded it again and compiled, this time it's giving me a different error.

nginx: [emerg] "modsecurity_rules_file" directive Rules error. File: /usr/local/owasp-modsecurity-crs/rules/REQUEST-901-INITIALIZATION.conf. Line: 298. Column: 119. Expecting an action, got: ctl:requestBodyProcessor=URLENCODED" in /etc/nginx/nginx.conf:62

@victorhora
Copy link
Contributor

@nix0x00

You are probably downloading libModSecurity 3.0.2 release? 3.0.2 doesn't support ctl:requestBodyProcessor=URLENCODED.

The support for this feature was added on this commit: f999f54

If you want to run the latest CRS you need to clone libModSecurity from the current master. You can follow the instructions here: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual-%28v2.x%29

@prajyodh
Copy link

I get the same error.
I have installed GeoIP-devel by sudo yum install GeoIP-devel
before configure and build module for nginx connector.
Modsecurity : Using v3/master
Nginx version : 1.14.1
ModSecurity-nginx : master

@victorhora
Copy link
Contributor

@prajyodh

Check if the Compilation Recipes helps you:

https://github.com/SpiderLabs/ModSecurity/wiki/Compilation-recipes-for-v3.x

Also check if using MaxMind instead works better. This issue might help you: #2041 (comment)

If your problem persists, please open a new issue and provide as many details as possible as per the issue template: https://github.com/SpiderLabs/ModSecurity/issues/new?template=bug-report-for-version-3-x.md

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RIP - Type - Usage Related with usage (not a bug)
Projects
None yet
Development

No branches or pull requests

3 participants