An upcoming PHP release is expected to fix two critical vulnerabilities, each rated 9.2 on CVSS v4.0. Are there any useful precautions to take before the release?
What should we do about the upcoming critical PHP security release?
Answers
I'd get ready to update PHP when the security release is available. Check which systems run it and make sure you have a way to test and deploy the update promptly.
The scores indicate serious issues, but they don't tell us from this information which configurations are affected or how the vulnerabilities work. Check the release notes for those details before assuming every installation has the same exposure.
Reply to this answer
One setting mentioned as a precaution is session.upload_progress.enabled. Turning it off may be worth considering if you don't use upload progress tracking, but the available information doesn't establish that the setting is related to either vulnerability.
Check whether your application relies on that feature before changing it, and don't treat the change as a substitute for the security update.
Reply to this answer
Taking a public site offline is an option if the risk of leaving it up outweighs the disruption. That's a pretty drastic move, though, and the limited details here don't establish that it's necessary for every PHP site.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions