News of two PHP vulnerabilities leaked during coordinated disclosure. Before the fix came out on 21 October, a researcher published what were claimed to be full technical details, and a distributor released images containing the fix early. Security firms also deployed protections for their customers ahead of time. This piece sets out the different views on embargoes and early publication, the relevant guidance and rules in the US, the EU and mainland China, and how Japan and Taiwan handle disclosure timing.
Based on 18 sources, including The PHP Foundation, The Register, The Record
On 21 October PHP released 8.5.12, 8.4.27, 8.3.36 and 8.2.35, fixing two vulnerabilities that may let an attacker who is not logged in run code on a web server. The vulnerability IDs leaked two days before the planned disclosure, and PHP moved the release forward by a day. The flaws are in PHP itself, so the PHP on the server is what needs updating, and people on hosted plans can check with their provider.
Based on 25 sources, including PHP, The PHP Foundation, WordPress.org
Eight intermediate certificates from the Indian certificate authority eMudhra had private keys smaller than 256, which anyone could compute at once and use to issue HTTPS certificates for other people's websites. After a researcher reported it on 17 October, Chrome and Firefox blocked them automatically within hours, with nothing for ordinary browser users to set up. Programs that do not go through a browser carry their own trust lists, and Node.js, Python's certifi, Go, Java and Linux distributions have been shipping updates since 19 October (not all complete as of 22 October), so people who write their own code or run servers need to update each one.
Based on 14 sources, including Mozilla dev-security-policy, Mozilla Bugzilla, Google