Horizon Alert
Summary of the vulnerability and why it matters
This advisory concerns a vulnerability in PHP-FPM that allows an unauthenticated remote attacker to potentially execute arbitrary code by crafting a malicious request. The issue arises from how PHP-FPM handles unread HTTP request bodies when backend connections are reused, enabling an attacker to inject parameters that can lead to code execution.
- A flaw allows a request to be split.
- Affects widely used web application components.
- Confirm if your web infrastructure is exposed.
Attack Path
How an attacker could exploit the issue
An attacker can exploit this vulnerability by sending a specially crafted multipart/form-data request to a web server running PHP-FPM with specific connection reuse settings. If the server reuses backend connections and PHP-FPM has an unread HTTP request body, the leftover data can be interpreted as a new request, allowing the attacker to forge parameters and potentially execute arbitrary PHP code.
- Requires unread request body.
- Smuggled request bypasses security controls.
- Code execution and request disruption.
Live Threat
Current exploitation, exposure, and threat context
When PHP-FPM does not fully read an HTTP request body, an attacker could potentially craft a request that, when the backend connection is reused by a front-end server, allows them to execute arbitrary PHP code on the server. This can occur when specific, non-default connection reuse configurations are enabled on web servers like Nginx or Apache.
- Unauthenticated remote code execution.
- Unread body bytes are parsed as new requests.
- Server compromise, including disruption of services.
Operational Fix
Recommended remediation, mitigation, and detection steps
The presence of PHP-FPM in web server architectures suggests that application owners, infrastructure teams, and potentially vendor-management teams should be involved. The immediate first step is to identify all instances of the affected PHP versions, determine if they are exposed externally or handle business-critical functions, and confirm the accountable owner for each instance before planning remediation.
- Identify affected PHP instances.
- Verify external reachability and criticality.
- Plan risk-based remediation.