Change directory permissions for temporary files about modsecurity-docker HOT 16 CLOSED

There is a workaround for this: use MODSEC_TMP_DIR: "/tmp".

from modsecurity-docker.

We ran into this issue when trying to upload a file through a modsecurity-crs nginx container. From the error log we got that modsecurity can't create a temporary file for processing the request body.

Turns out this is not because of permissions, but because the entire /tmp/modsecurity/{data,upload,tmp} directory structure doesn't exist in the container.

Same goes for the apache variant.

from modsecurity-docker.

We ran into this issue when trying to upload a file through a modsecurity-crs nginx container. From the error log we got that modsecurity can't create a temporary file for processing the request body.

Turns out this is not because of permissions, but because the entire /tmp/modsecurity/{data,upload,tmp} directory structure doesn't exist in the container.

Same goes for the apache variant.

This issues still occurs. The directories are existent as shown below.

@fzipi Please is there any fix for this?

Thanks.

from modsecurity-docker.

Ugh, taking a look, thanks.

from modsecurity-docker.

@bfamzz Can you add which version are you using?

from modsecurity-docker.

Thanks for your response @fzipi

The versions are as follows:

• Modsecurity: v3.0.5
• Modsecurity Connector: v1.0.2
• OWASP CRS: v3.3.2

This is shown in the screenshot below.

from modsecurity-docker.

Excellent. I was just talking about which container you were pulling, but I can infer that from this data ;)

from modsecurity-docker.

@bfamzz I can't reproduce the problem in nginx-modsec3. But there is a permissions problem with the apache default container (I'm verifying the alpine one).

Can you paste here which version of the container are you using? Is it the alpine version? Can you get me the image ID?

from modsecurity-docker.

Hello @fzipi

Container version: owasp/modsecurity-crs:3.3.2-nginx
Image ID: da8b2b5b5f1f

Please see the screenshot below:

I will try and pull the image again. The most recent image is from 3 days ago. Mine is from 9 days ago.

I will update you shortly.

Thanks.

from modsecurity-docker.

Hi @fzipi

This is the new image ID

However, the issue is still occuring.

Directory permission

Image used by the running container

from modsecurity-docker.

Thanks, I could reproduce it now. Fixing.

from modsecurity-docker.

Just to have all the context: docker-library/httpd#10. I think upstream is doing it wrong :/

from modsecurity-docker.

Hi @fzipi

Just to confirm, is the issue fixed in the recent most recent image (6 hours ago)

Thanks.

from modsecurity-docker.

Hey @bfamzz ! The issue should be fixed for the base container, yes. The crs container will be building in top of that one.

from modsecurity-docker.

Alright. Thanks.

from modsecurity-docker.

Just to document it here, upstream merged my fix so this should not be a problem anymore.

from modsecurity-docker.