#99347Add HTTP host header injection check to reports module
Description
In case the web server scenario is not properly configured to deny
HTTP host header injection, and the trustedHostsPattern is not explic
enough, an corresponding check in the reports module will issue
an error message like
HTTP_HOSTcontained unexpected “a0a3aa2f59.random.example.org”SERVER_NAMEcontained unexpected “a0a3aa2f59.random.example.org”
Using the configuration directive UseCanonicalName On for Apache
web server environments mitigates the risk.
This is related to a side note in https://typo3.org/security/advisory/typo3-core-sa-2014-001
which introduced the trustedHostsPattern configuration.
Reviews 6
- 10.4 77160[BUGFIX] Fix absolute backend URL generation in frontend context
- 11.5 77159[BUGFIX] Fix absolute backend URL generation in frontend context
- 12.1 77114[TASK] Add HTTP host header injection check to reports module
- 10.4 77038[TASK] Add HTTP host header injection check to reports module
- 11.5 77025[TASK] Add HTTP host header injection check to reports module
- main 77024[TASK] Add HTTP host header injection check to reports module