> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/suspicious-failed-http-request-potential-spring4shell-exploit.md).

# Suspicious failed HTTP request - potential Spring4Shell exploit

### Synopsis

| Field                | Value                                                                                                   |
| -------------------- | ------------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                                 |
| Training Period      | 30 Days                                                                                                 |
| Test Period          | N/A (single event)                                                                                      |
| Deduplication Period | 1 Day                                                                                                   |
| Required Data        | <p>Requires one of the following data sources:<br>Palo Alto Networks Firewall EAL Logs OR XDR Agent</p> |
| ATT\&CK Tactic       | Initial Access (TA0001)                                                                                 |
| ATT\&CK Technique    | Exploit Public-Facing Application (T1190)                                                               |
| Severity             | Low                                                                                                     |

### Description

A potentially malicious failed HTTP request was received, possibly as part of a Spring4Shell exploitation attempt.

### Attacker's Goals

Gain the ability to execute code remotely or drop malware.

### Investigative actions

* Check if suspicious process executions occurred after the request.
* Consider limiting access to the vulnerable server.

### Variations

<details>

<summary>Suspicious HTTP request - potential Spring4Shell exploit</summary>

**Synopsis**

| Field             | Value                                     |
| ----------------- | ----------------------------------------- |
| ATT\&CK Tactic    | Initial Access (TA0001)                   |
| ATT\&CK Technique | Exploit Public-Facing Application (T1190) |
| Severity          | Medium                                    |

**Description**

A potentially malicious HTTP request was received, possibly as part of a Spring4Shell exploitation attempt.

**Attacker's Goals**

Gain the ability to execute code remotely or drop malware.

**Investigative actions**

* Check if suspicious process executions occurred after the request.
* Consider limiting access to the vulnerable server.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/suspicious-failed-http-request-potential-spring4shell-exploit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.