Content
You are here:
SecureFlag issue
Added by Daryl du Plessis over 6 years ago
Hi,
I recently had a security audit performed on our Open Project server installation and overall the security level is good except for the SecureFlag issue. This is where the cookie used to identify the user’s session “_open_project_session” is not flagged as secure and could allow for a MITM hijacking of the session. Is it possible for this to be changed or a mitigation of some sort (change to a setting)? See this link for more info:
Replies (3)
Hi Daryl,
thanks for the report. This is indeed an issue since the
secure
flag is not tied to theSetting.protocol
option in OpenProject (configured automatically by the packaged installation when you set up SSL, for example).You currently need to set the configuration
rails_force_ssl
. To do that in the packaged installation, run the following command:In a manual installation, export it as an ENV var instead (or set in config/configuration.yml).
This is tracked in to fix in 7.4.5 and make this flag the default whenever https is set.
Any chance you have a result of that audit that you can make available to us?
Best,
Oliver
Hi Oliver,
Thanks for the quick response. I have made the recommended changes.
The assessment didn’t find anything else of significance with the OP server, so that is good. I will not be able to send you the details as it contains sensitive information regarding the internal network etc.
Regards
Daryl
Hi Daryl,
thanks for the info and no worries regarding the details. We will release a 7.4.5 that will automatically set that flag for all users likely today.
Best,
Oliver