My host says it applied server-level hotfixes to its web-facing PHP packages, but the PHP version number hasn't changed. Can that be legitimate, and how can I verify that the sites are actually protected?
Can PHP be patched even if the version number hasn't changed?
Answers
Yes. A package maintainer can backport a security fix into an existing PHP branch without changing the upstream PHP version shown by phpinfo(). The package release or build number may change instead. An older-looking version is not proof that the fix is missing, and the version string alone doesn't prove it's present either.
The catch is that you need to know which vendor built the package and which package release your site actually uses. An upstream version check by itself can give a false alarm for a backported fix.
Reply to this answer
Ask the host for the package name, exact package release or build, and the vendor advisory or change record covering each CVE. Also ask them to confirm that your site's web-facing PHP process is running that build. A generic assurance that every version is protected isn't much to verify against.
If the host says it's a server-level mitigation rather than a patch in the PHP package, ask what layer provides it, which configurations it covers, and whether there are any exceptions.
Reply to this answer
Make sure you're checking the PHP used by the website, not just the command-line PHP. Hosts can have multiple builds installed. A temporary phpinfo() page can help identify the web-facing runtime, but remove it afterward because it exposes configuration details.
Once you know the runtime, compare its package build with the host's documented fix. If you don't have access to package details, the host needs to provide them.
Reply to this answer
This does make vulnerability scanning less straightforward. A scanner that only compares the displayed PHP version with upstream fixed versions might flag a backported package anyway. Check the vendor's package advisory before treating that result as conclusive, but don't dismiss it without evidence either.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_j57!copperthimble.4:
That distinction matters. A mitigation outside PHP may block a particular attack path without changing the PHP binary itself.