On this page (7 sections)

Ubuntu has published security notice USN-9055-1 about pecl_http, a PHP extension. According to the notice, the extension incorrectly handled certain HTTP request parameters, which led to a type confusion.

If you run PHP applications on Ubuntu servers, you should check whether this extension is installed and loaded, and then read the notice to see whether an update is listed for your release. Very little detail is public so far, and this article sticks to what the notice actually says.

What Ubuntu says happened

The Ubuntu notice is short. It states that pecl_http incorrectly handled certain HTTP request parameters, leading to a type confusion. It adds that a remote attacker could possibly use the issue to make PHP crash, causing a denial of service, or to execute arbitrary code.

The wording is cautious: the attacker could "possibly" achieve code execution. The text we reviewed does not say that attacks are happening, and it gives no CVE identifier, severity score, affected Ubuntu releases, or affected and fixed package versions. Treat anything beyond the points above as unconfirmed. Only one publisher, Ubuntu itself, covers this so far, so there is no independent confirmation or additional technical analysis yet.

What a type confusion means in general

This section explains the weakness class in general terms; it is not a description of how this specific bug works, which the notice does not give. Type confusion happens when a program expects a value to be one kind of data, such as a string, but treats it as another, such as an array or object. Because different types are laid out differently in memory, the code can read or write memory in ways its author never intended.

In native code such as a PHP extension, that class of bug can generally end in a crash or, in worse cases, memory corruption that could be turned into code execution. These two outcomes match what Ubuntu describes. Whether code execution is practical here is not stated in the notice.

Who is realistically exposed

Based on the notice alone, the only safe conclusion is that servers where the pecl_http extension is installed and loaded are the ones that could be affected. The notice does not say which Ubuntu releases or package versions are involved, and it does not describe which request parameters or application patterns trigger the problem. If the extension is not installed or loaded on a server, this notice does not point to a direct risk there.

The first job is therefore to find out whether you have the extension at all.

How to check if you are affected

This command lists the PHP modules loaded by your command-line PHP and shows a match if the http extension is present. Run it on the server; no output means the CLI PHP does not load it.

Check whether the http (pecl_http) extension is loaded in CLI PHPShell
php -m | grep -i '^http$'

The command-line PHP can use a different configuration from your web server, so also check the web runtime. You can use your hosting panel's PHP information view, or a temporary page that calls phpinfo(), and look for an http section. Remove any temporary page afterwards.

This command asks the Debian and Ubuntu package manager which installed packages have names containing both php and http. Run it to see whether a packaged build of the extension is installed. Package names vary, so read the results rather than assuming a name.

List installed packages matching php and http (Debian/Ubuntu)Shell
dpkg -l | grep -i php | grep -i http

If you installed the extension through PECL rather than apt, this command lists PECL-installed extensions and their versions.

List extensions installed through PECLShell
pecl list

What to do now

The research does not confirm which Ubuntu releases are affected or whether a fixed package exists, so verify this in the full notice and through your normal Ubuntu update channel instead of guessing version numbers.

  1. Find out whether pecl_http is installed and loaded on each server, using the checks above.
  2. Open USN-9055-1 and check whether it lists your Ubuntu release and, if so, which package versions are updated.
  3. If an update is available for your release, refresh package lists and apply it on affected systems.
  4. After updating, restart PHP-FPM or Apache if needed so the new extension version is loaded.
  5. If you installed the extension through PECL rather than apt, work out how it will be updated, since an apt upgrade will not change a PECL install.
  6. If you do not use the extension, consider disabling or removing it to reduce your attack surface.
  7. Review PHP and web server error logs for unexplained crashes or segmentation faults.

This pair of commands refreshes the package index and then upgrades installed packages on Ubuntu. Run it with administrator rights and check the proposed list before confirming. It only helps if Ubuntu has published an update for your release.

Apply available updates (Ubuntu)Shell
sudo apt update && sudo apt upgrade
Caution. Restarting PHP-FPM or Apache drops in-flight requests. Do it in a maintenance window or behind a load balancer, and replace the service name with the one your server uses (for example a versioned php-fpm service).

After any update and restart, run the module check again to confirm the extension loads without errors and your sites still respond normally.

Detection and monitoring afterwards

Because the flaw is described as able to crash PHP, repeated PHP worker failures are a useful signal. This command searches the system log for segmentation faults mentioning PHP. Run it on the server and look for repeated entries with timestamps that line up with odd web requests. The log path may differ on your system.

Search system logs for PHP segmentation faultsShell
sudo grep -i 'segfault' /var/log/syslog | grep -i php
  • Watch for sudden spikes in 5xx errors or PHP-FPM worker restarts.
  • Compare web server access logs around any crash to find the requests that coincided with it.
  • If you suspect code execution, look for new or modified files in web directories and unexpected outbound connections, and follow a compromise checklist such as website hacked: what to do.

Outside-in checks can help you notice symptoms such as downtime or changed pages, though they cannot see which extensions run on your server. Uptime monitoring can flag repeated crashes that take a site offline, and a free malware scan can help check public pages after an incident. A web application firewall adds a layer in front of PHP, but it is not a substitute for updating; see what is a WAF.

What is still unknown

  • No CVE identifier or CVSS severity score appears in the research.
  • Affected Ubuntu releases and affected or fixed package versions are not in the research; consult the Ubuntu notice.
  • Whether an update is available for your release must be verified in the notice.
  • The notice does not say whether the flaw is being exploited.
  • Which request parameters trigger the bug, and how reliable code execution would be, are not described.

Until more detail is published, the risk is real but unquantified. Checking whether you load the extension is quick and tells you whether this matters to you.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. USN-9055-1: pecl_http vulnerabilityubuntu.com ·
  • Ubuntu
  • PHP
  • USN
  • pecl_http
  • type confusion