MAXIMUM ALERT ON YOUR SERVER

MAXIMUM ALERT ON YOUR SERVER

PHP vulnerabilities, dubbed “PHP2Shell” (with a third, rarer but much nastier one identified later), made headlines.

PHP released security updates, in the form of version updates such as:

• PHP 8.5 which must upgrade to 8.5.12

• PHP 8.4 to 8.4.27

• PHP 8.3 to 8.3.36

• Etc.

…

Ahem… Ahem!

Please excuse the Boss, but I’ll try to make his jargon-filled explanations more digestible:

YES, the whole world was indeed hit by a series of computer vulnerabilities specific to the language known as “PHP.”

All media, even BFM TV, reported on it, and especially on the immediate consequences like service interruptions and, even worse.

NO, even if your site is perfectly built, nothing will prevent the famous vulnerability because it’s at the server level itself, meaning the “hotel” hosting your site (more precisely, the PHP interpreter, the “concierge” of the “hotel”).

HOWEVER, the Boss reminds you that 70% of websites worldwide are built with PHP, so you’re not alone in this turmoil.

Does that do you any good?

Us neither!

FORTUNATELY,

Lionel, our System Engineer, guarantor of our servers’ smooth operation, reacted immediately!

He implemented all the new versions as soon as the PHP company released its updates.

This saved YOU from service interruptions, outages, and other unpleasantries that massively paralyzed websites worldwide (due to vulnerabilities or as a precaution, like many government sites).

YES, you can breathe now: everything is fine, you’re on CybSyn Airlines.

More seriously,

The Boss would like to take this opportunity to thank his colleague and friend once again, without whom CybSyn would not exist in its primary activity of hosting:

Ladies and Gentlemen,

for Lionel,

a round of applause!

(Thanks also to Google Wiz who discovered the vulnerabilities quickly).

For the curious, do you know what exactly you escaped?

1. A hacker could execute commands on the server remotely without needing to authenticate.

2. They also had the ability to directly read the memory of running PHP processes, risking the compromise of all authentication information of other users.

3. You could have done absolutely NOTHING to prevent this on your site, as the vulnerability is located at the server level, meaning the physical support that hosts websites.