1. A Flaw in the Code Behind Most Websites Will Be Patched on Your Vendors' Schedule, Not Yours
On October 21st the maintainers of PHP, the programming language behind a majority of websites, released fixes for two critical flaws that let an attacker take over a server without logging in. Palo Alto Networks has shipped no fixed release for its firewall software, and Cisco and Fortinet are still working out which of their products are affected.
You may have patched your own websites, or whatever else you built with PHP. Your firewall's management console, the security appliance's admin page, or anything else that arrived with PHP built in is a different matter, because only the company that sold it can fix it, and the biggest vendors had not as of October 22nd. Palo Alto Networks says every version of its firewall software is affected, has no fixed release, and is not aware of malicious exploitation. Cisco has 18 products and 13 cloud services under investigation, lists none as vulnerable or as confirmed safe, and offers no workaround. Fortinet says its main firewall operating system is not affected, but it is still investigating about a dozen other products, and a clear operating system says nothing about the management consoles and add-on products around it. Anything past end of support or end of life most likely will not get a PHP upgrade at all, and neither will a product whose maker no longer exists. Treat those as rip and replace.
The flaws sit in PHP itself, the engine that runs the code behind a website. W3Techs, a web-technology survey, counts it on about 70% of the sites whose server language it can identify. An attacker needs no login, and on a common Apache web-server setup a single crafted request triggers the bug before any of the site's own code runs. Updating WordPress, a plugin or your own application therefore changes nothing. The engine underneath has to be replaced by whoever controls the server software. If your site runs on a hosting plan or a virtual private server, that is the hosting company, and you can update everything you own and still be exposed until it upgrades PHP. When PHP is built into a vendor's product, only the vendor can replace it. PHP 8.1 and older get no official fix.
The flaws were found partly with AI models, and the first exploitation attempt came before the fixes did. Amazon's honeypot network, a set of decoy servers it uses to watch attacks, logged an exploitation attempt on October 17th, four days before the fixes were released, and Amazon does not know how the actor got the information. The flaws' identifiers leaked on October 20th, and Calif, a security firm, accidentally published a demonstration video that day. A related third flaw, disclosed October 23rd, has only a temporary workaround until the next release.
Whether anyone has actually been breached is in dispute. The US Cybersecurity and Infrastructure Security Agency (CISA), in an alert last revised October 23rd, says it "has not observed successful exploitation of these vulnerabilities in the wild" as of publication. CrowdStrike has seen testing, probing and unsuccessful attempts, and says many public proofs of concept crash the server rather than run code; if a reliable one appears, many actors "will almost certainly" use it. Sansec, an e-commerce security firm, now calls mass exploitation "less likely than we first expected." Against that, Wiz, a cloud security firm, demonstrated code execution on WordPress, Drupal and Joomla website platforms. ELLIO, a security firm, saw a web shell, a backdoor an attacker leaves behind, staged within 81 minutes of a first hit. CrowdStrike's chief executive George Kurtz told CNBC to expect "a lot of breaches happening in the coming months."
Most Linux distributions fixed their packages, but Red Hat, Amazon Linux and SUSE had not as of October 22nd. CISA's guidance is to inventory all PHP, which it notes is often a component of other software, patch internet-facing systems first, and take offline anything that cannot be patched. PHP lists temporary workarounds for server administrators, and a web application firewall, a filter that blocks malicious web traffic, "may provide some protection," in CISA's words, though Sansec says its own cannot see these requests because they are handled before application code. Wiz compares the episode to Log4Shell, the 2021 flaw buried in software dependencies. The comparison fits on one point: PHP sits inside products you did not write, and the vendor's advisory is the only place to learn whether a product bundles it and when a patch will come, if it ever will.