📊 Quantitative test results for language: eng, year: 2023, size: 10K, paranoia level: 1:
🚀 Quantitative testing did not detect new false positives

Yes, removing duplicates makes sense.

Done, I got a few more ideas after removing duplicates so I've made some improvements.

Do we really want to block phpinfo.php at PL1?

Rest is very cool.

@dune73 I think it's fine since it's only targeting REQUEST_FILENAME and this file shouldn't be accessed on a production system anyways. We're already blocking phpinfo.php at PL-1 by 933150 but that was most likely not intentional which is why I added it to restricted-files.data just in case the behavior of that rule changes.

In the case of CVE-2023-49103 accessing this file can result in the admin password, email password, and database password being leaked in containerized deployments and not just the configuration of PHP.

I was not aware of CVE-2023-49103. It's still a tough call for me (since it's used as a PoC of successful installation by so many people), but this CVE tilts it in favor of blocking for me.

What is needed here? Do we merge?

@fzipi I'm just waiting for someone to review and approve. Everything else is ready.