Bug ID 685174: When script-src does not exist, FPS creates the script-src directive while ignoring the policy defined by default-src

Last Modified: May 01, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP FPS(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5

Fixed In:
14.0.0

Opened: Sep 24, 2017
Severity: 3-Major

Symptoms

When script-src does not exist, FPS creates the script-src directive while ignoring the policy defined by default-src. This is also true for other directives such as img-src, style-src, etc.

Impact

Application might not work because of FPS restricting inline script execution.

Conditions

Content-Security-Policy configured as follows: Content-Security-Policy: default-src 'unsafe-inline' For example, for the following header: default-src 'unsafe-inline' FPS modifies it to: default-src 'unsafe-inline'; script-src 'self' 'nonce-RANDOM-VAL'

Workaround

None.

Fix Information

The 'unsafe-inline' will not be injected into script-src or style-src directives if it is present in default-src directive.

Behavior Change