Issue Bug Closed

#105856CSP reports may flood database

Sadik Asbach 12/20/24, 10:47 updated 08/12/25, 14:35

Description

Well formed CSP reports are by default always written to the database and thus may flood it (as I already described/asked here: https://talk.typo3.org/t/solved-possibility-to-deactivate-db-logging-of-csp-reports/6041 ).
You can prevent, and deal with it, but I think it makes sense to have the the logging 1) disabled by default and 2) optionally enabled (e.g. in the site-specific csp.yaml) when configuring CSP. As I was not aware of it, it may thus make more administrators aware of the logging. And prevent offline websites/services due to a full database.

Reviews 4

History 513

  1. Garvin Hicking commented <span data-processor="relativetime" data-value="2024-12-20T11:14:04+00:00" > 12/20/24, 11:14 </span>

    In my opinion, it needs to be enabled by default, otherwise CSP would block things you’re not aware off. Doing log rotation/clearing is IMO a task for system maintainers, and watching that for abuse.

    (The link offers some solutions how logging can be influenced)

  2. Oliver Hader commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-02-05T13:25:14+00:00" > 02/05/25, 13:25 </span>

    Applied in changeset commit:e4a39fd2087c57363e2e7dee15bca0044e324cb2.