Name:Large HTTP POST Request Resulting in Server Error id:284ab19f-15f6-4f1c-9a4d-9f331438e37d version:1 date:None author:Raven Tait, Onur Mustafa Erdogan, Nasreddine Bencherchali, Splunk status:production type:Anomaly Description:This analytic detects HTTP POST requests with a body of at least one megabyte that receive an HTTP 500 response.
Large failed uploads can indicate attempts to trigger resource exhaustion or exploit vulnerable request handling, including behavior associated with PHP2Shell, but require investigation with related web and application logs. Data_source:
| stats count min(_time) as firstTime max(_time) as lastTime max(body_bytes) as body_bytes values(user_agent) as user_agent values(status_code) as status_code
how_to_implement:Zeek HTTP logs must be ingested into Splunk using the latest version of Splunk Add-on for Zeek (https://splunkbase.splunk.com/app/5466).
The "post_body" field must be populated, which requires Zeek to be configured with the HTTP post body extraction policy.
Configure the `zeek_http` macro to match the sourcetype used by your Zeek add-on. known_false_positives:Large legitimate uploads can fail because of application limits, timeouts, storage constraints, or transient server errors.
Review the request URI, upload size, server logs, and client behavior before classifying the activity as malicious. References: -https://www.php2shell.com/ -https://github.com/php/php-src/commit/3584a98bda0f2c0d367255b046798b0d3a221a19 -https://docs.zeek.org/en/master/logs/http.html drilldown_searches:
: analytic_story:['PHP2Shell']