{"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\n The PEAR repository<\/a> (currently offline until the compromise can be remedied) is a site that holds host to a vast number of PHP projects where programmers and application developers use the go-pear script to download PHP class packages from the repository. This library of code was intended to promote a standard coding style. While community-driven, the PEAR project has a PEAR group acting as the governing body handling administrative tasks. A PEAR package is essentially a gzipped tar file consisting of source code written in PHP and can be readily used by developers as ordinary third-party code by way of include statements in PHP. Users could invoke the PEAR package manager from the command line via the Speculated to have happened as far back as 6 months ago, a malicious user compromised the PEAR installation script with an extractor that enabled a backdoor (via Perl) that opened a shell connecting to a remote infected server. This allowed the malicious users to install apps, run malicious code, and capture sensitive data. <\/p>\n\n\n\n If you’re a user who has built your PHP RPMs from the PEAR website, there is a potential chance that your machine may have been compromised. DCSO<\/a> (a German cybersecurity organization) has published a MISP (Malware Information Sharing Platform) event with the relevant IOCs (indicators of compromise) that can be used to scan your infrastructure for infections:<\/p>\n\n\n\n cPanel & WHM users have nothing to fear, as we build our RPMs from GitHub, which does not pull in the compromised go-pear.phar archive to our RPMs. This means there are no indications that any cPanel RPMs containing PEAR packages are compromised. <\/p>\n\n\n\n For further updates from PEAR directly, we recommend following the official pear Twitter feed<\/a>. You can also join in the discussion by participating in our Discord<\/a> and Slack<\/a> channels, as well as our official cPanel subreddit.<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" As you may or may not be aware, on January 19th, 2019, a security announcement was published confirming the compromise of the PHP Extension and Application Repository (PEAR) installation script. The PEAR project had the following statement to announce: “A security breach has been found on the http:\/\/pear.php.net webserver, with a tainted go-pear.phar discovered. The PEAR website itself has […]<\/p>\n","protected":false},"author":77,"featured_media":65093,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[49],"tags":[2185,297,325],"class_list":["post-51701","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-products","tag-pear","tag-php","tag-product-development"],"acf":[],"yoast_head":"\nWhat is PEAR?<\/h2>\n\n\n\n
pear<\/code> command. For PHP installations running on Linux, the PEAR package manager is enabled by default.<\/p>\n\n\n\n
So what happened?<\/h2>\n\n\n\n
<\/figure>\n\n\n\n
Should I be concerned?<\/h2>\n\n\n\n
\u201cPHP PEAR Software Supply Chain Attack\u201d (5c46dd16-2ed0-4604-ab12-181cac12042b)<\/code><\/p><\/blockquote>\n\n\n\n