Skip to main content

Vulnerabilities in PHP, Node.js and TLS: when the flaw is technical, but the risk is a governance one

Vulnerabilities in PHP, Node.js and TLS: when the flaw is technical, but the risk is a governance one

In a matter of weeks, three pillars of the internet were shaken at the same time.

On Wednesday (the 21st), two critical flaws in PHP, the language behind about 70% of the world’s websites, led governments and organizations to take systems offline as a precaution.

The vulnerabilities had been hidden for more than a decade and were found with the help of artificial intelligence. In Brazil, Anatel took the SEI system offline for about ten hours to apply the fix.

On the same day, Node.js published fixes for ten vulnerabilities, four of them high severity, involving DNS, TLS certificate verification and Brotli decompression, with a risk of remote code execution.

A few days earlier, Google revealed that attackers had compromised domain registry operators in three countries and obtained fraudulent TLS certificates for domains belonging to Google and other major brands.

Three different technologies, three different origins and one question for those in leadership.

Would your company be able to say, within a few hours, whether it was affected?

Applying the patch is IT’s responsibility. But when the alert arrives, the first questions are not technical. Where does this component run in our operation? Who is responsible for each system? What is the business impact if it goes offline? Who decides between updating now or suspending the service? Who informs the board, the customers and the regulator?

In the PHP case, the security agencies themselves recommended updating immediately or, where that was not possible, considering taking the sites down. That is a risk decision, weighing business continuity against exposure, and it cannot be improvised by whoever has the server open on the screen.

The speed has changed as well. With AI accelerating the discovery of flaws, and experts warning that the same evolution may accelerate the preparation of attacks, the window between disclosure and exploitation tends to shrink. Companies that depend on spreadsheets, e-mails and the memory of whoever knows the environment arrive late to this race.

Where governance comes in

GRCtech does not apply the patch. It structures the layer that lets the company decide and act quickly, connecting risks, controls, third parties, continuity and evidence in a single base. In practice, that means:

  • Assets linked to risks. With the inventory of systems and technologies associated with risks and owners, the company stops spending hours finding out where PHP or Node.js is running;
  • Prioritization by business impact. Not every fix has the same urgency. It is the criticality of the system to the operation that sets the order, not the order in which tickets arrive;
  • Third parties under monitoring. The certificate case shows that trust in external infrastructure is also a risk to be governed continuously;
  • Coordinated response. Roles, action plans and evidence defined before the incident, so that recovery does not depend on executive panic.

Checklist for decision-makers

  • Keep a continuous inventory of applications, dependencies and versions in use;
  • Set deadlines for fixing critical vulnerabilities based on a business risk matrix;
  • Review the governance of digital certificates and keys, including who monitors certificate issuance for your domains;
  • Also track unsupported versions, which remain vulnerable even after the fixes;
  • Bring IT into the risk and governance committee, not just into the ticket channel.

Lessons learned

Information security is not built with tools alone. It is built with integrated processes and governance. The next critical vulnerability will arrive, and what will separate a company that reacts from one that responds is what it structured beforehand.

How does your company prioritize a critical vulnerability today when it is disclosed? Find out how GRCtech structures that response.

João Paulo Spader Back, Executive Director at SinapseTech