{"id":51701,"date":"2019-02-07T13:00:42","date_gmt":"2019-02-07T19:00:42","guid":{"rendered":"https:\/\/blog.cpanel.com\/?p=51701"},"modified":"2019-02-07T13:00:42","modified_gmt":"2019-02-07T19:00:42","slug":"when-php-went-pear-shaped-the-php-pear-compromise","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/products\/when-php-went-pear-shaped-the-php-pear-compromise\/","title":{"rendered":"When PHP Went Pear Shaped- The PHP PEAR Compromise"},"content":{"rendered":"\n
As you may or may not be aware, on January 19th, 2019, a security announcement<\/a> was published confirming the compromise of the PHP Extension and Application Repository (PEAR) installation script. The PEAR project had the following statement to announce:<\/p>\n\n\n\n “A security breach has been found on the http:\/\/pear.php.net<\/a> webserver, with a tainted go-pear.phar discovered. The PEAR website itself has been disabled until a known clean site can be rebuilt. A more detailed announcement will be on the PEAR Blog once it\u2019s back online.”<\/p><\/blockquote>\n\n\n\nWhat is PEAR?<\/h2>\n\n\n\n