Project

General

Profile

Actions
Copy link

Task #73047

closed

Content-Security-Policy for the Backend

Added by Peter Proell almost 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Security
Target version:
-
Start date:
2016-01-31
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

There is still (7.6) CSP Issues in the backend (/typo3) and I am wondering why ticket 63712 has been closed.
We should add a fitting CSP to the .htaccess in /typo3. Currently I am adding

Header set Content-Security-Policy "default-src * 'unsafe-eval' 'unsafe-inline';

in /typo3/.htaccess to overrule the more strict CSP of the website itself and make the backend work as well.
It would be a nice security feature if the TYPO3 backend would support a stricter CSP.

Infos on CSP:

Related issues 2 (1 open — 1 closed)

Related to TYPO3 Core - Task #63712: Avoid use of eval() and replace itClosed2015-09-30

Actions
Related to TYPO3 Core - Epic #87417: Integrate proper Content Security Policy (CSP) handlingNewOliver Hader2019-01-13

Actions
Actions
Copy link

Also available in: Atom PDF