# CVE-2017-9791: Apache Struts 1 Improper Input Validation

> Remote attackers can execute arbitrary code via malicious field values in Apache Struts 1 plugin messages, requiring immediate upgrades.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 10 Feb 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-29rm-6752-gvwv

## What is CVE-2017-9791?

CVE-2017-9791 is a critical code injection vulnerability in Apache Struts, published on 10 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Struts 1 plugin in Apache Struts 2.1.x and 2.3.x might allow remote code execution via a malicious field value passed in a raw message to the ActionMessage.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-9791?

2 open source packages ship an affected version, including org.apache.struts:struts2-struts1-plugin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.struts:struts2-struts1-plugin` | Maven | All versions to 2.3.37 | None |
| `org.apache.struts:struts2-struts1-plugin` | Maven | All versions to 2.3.37 | None |

Products: Apache Struts.

## How do I fix CVE-2017-9791?

No fix has been published for CVE-2017-9791 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Aug 2022.

## Is CVE-2017-9791 being exploited?

Yes. Attackers have exploited CVE-2017-9791 in the wild since at least 10 Feb 2022.

Public exploit code:

- CVE-2017-9791 (github_poc): https://github.com/dragoneeg/Struts2-048
- Apache struts struts 2 048, CVE-2017-9791. (github_poc): https://github.com/IanSmith123/s2-048
- Apache Struts 2.3.x Showcase - Remote Code Execution (exploitdb)
- Apache Struts 2 Struts 1 Plugin Showcase OGNL Code Execution (metasploit)
- Metasploit module for Apache Struts CVE-2017-9791 Remote Code Execution Vulnerability (github_poc): https://github.com/xfer0/CVE-2017-9791
- Apache Struts 2 - Struts 1 Plugin Showcase OGNL Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in Apache Struts

- [CVE-2020-17530](https://insights.sbomify.com/CVE-2020-17530/): Apache Struts Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-5638](https://insights.sbomify.com/CVE-2017-5638/): Apache Struts Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-0391](https://insights.sbomify.com/CVE-2012-0391/): Apache Struts 2 Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2018-11776](https://insights.sbomify.com/CVE-2018-11776/): Apache Struts Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2017-9805](https://insights.sbomify.com/CVE-2017-9805/): Apache Struts Deserialization of Untrusted Data (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9791 and fix it if it is affected.

What it is: CVE-2017-9791 is a critical code injection vulnerability in Apache Struts, published on 10 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-9791 in the wild since at least 10 Feb 2022.

Affected packages and fixed versions:
- org.apache.struts:struts2-struts1-plugin (Maven): affected all versions up to 2.3.37; no fix listed
- org.apache.struts:struts2-struts1-plugin (Maven): affected all versions up to 2.3.37; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9791/ (Markdown: https://insights.sbomify.com/CVE-2017-9791/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9791
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9791
- OSV: https://osv.dev/vulnerability/CVE-2017-9791

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9791/
Summaries are generated and may contain mistakes; the official description above is the record.