[checkmk-commits] [tribe29/checkmk] 4d76a6: 13903 SEC Introduce additional CSRF checks

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 4d76a610e14dbf0cf80a413b4dbe6229be3835a6 https://github.com/tribe29/checkmk/commit/4d76a610e14dbf0cf80a413b4dbe6229b… Author: Maximilian Wirtz <maximilian.wirtz(a)tribe29.com> Date: 2022-05-27 (Fri, 27 May 2022) Changed paths: A .werks/13903 M cmk/gui/node_visualization.py M cmk/gui/sidebar/__init__.py M cmk/gui/valuespec.py M cmk/gui/views/__init__.py M cmk/gui/wato/pages/activate_changes.py M cmk/gui/wato/pages/folders.py M cmk/gui/wato/pages/host_diagnose.py M cmk/gui/wato/pages/services.py M cmk/gui/wato/pages/user_profile/async_replication.py M cmk/gui/wato/pages/user_profile/mega_menu.py M tests/unit/cmk/gui/test_sidebar.py M web/htdocs/js/modules/dashboard.js M web/htdocs/js/modules/host_diagnose.ts M web/htdocs/js/modules/service_discovery.ts M web/htdocs/js/modules/sidebar.js Log Message: ----------- 13903 SEC Introduce additional CSRF checks Previous to this Werk most data changing requests needed a transaction id. This mechanism was not used in all methods and in some cases the transaction id mechanism was not a good fit. So now a new CSRF token is introduced and checks are implemented in various locations. If you scripted the UI you need to parse the CSRF token from the HTML and send it with the Post requests. Change-Id: Ic709514c4e0f00c1aeeeede8aaf4c388007fcd7a