5fbbd3dd6e
A nonce-based Content-Security-Policy thwarts XSS attacks by allowing
inline JavaScript to execute if the script nonce matches the header
value. Rails 5.2 supports nonce-based Content-Security-Policy headers,
so provide configuration to enable this and make it work.
To support this, we need to change all `:javascript` HAML filters to the
following form:
```
= javascript_tag nonce: true do
:plain
...
```
We use `%script` throughout our HAML to store JSON and other text, but
since this doesn't execute, browsers don't appear to block this content
from being used and require the nonce value to be present.
15 lines
620 B
Ruby
15 lines
620 B
Ruby
# frozen_string_literal: true
|
|
|
|
csp_settings = Settings.gitlab.content_security_policy
|
|
|
|
if csp_settings['enabled']
|
|
# See https://guides.rubyonrails.org/security.html#content-security-policy
|
|
Rails.application.config.content_security_policy do |policy|
|
|
directives = csp_settings.fetch('directives', {})
|
|
loader = ::Gitlab::ContentSecurityPolicy::ConfigLoader.new(directives)
|
|
loader.load(policy)
|
|
end
|
|
|
|
Rails.application.config.content_security_policy_report_only = csp_settings['report_only']
|
|
Rails.application.config.content_security_policy_nonce_generator = ->(request) { SecureRandom.base64(16) }
|
|
end
|