# CVE-2016-3087: Apache Struts vulnerable to arbitrary remote code execution due to improper input validation > Remote attackers can execute arbitrary code via the REST Plugin when Dynamic Method Invocation is enabled. - **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Jun 2016 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-mmj6-cjj4-hpr5 ## What is CVE-2016-3087? CVE-2016-3087 is a critical code injection vulnerability in Apache Struts, published on 7 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Apache Struts 2.3.19 to 2.3.20.2, 2.3.21 to 2.3.24.1, and 2.3.25 to 2.3.28, when Dynamic Method Invocation is enabled, allow remote attackers to execute arbitrary code via vectors related to an ! (exclamation mark) operator to the REST Plugin. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2016-3087? 6 open source packages ship an affected version, including org.apache.struts:struts2-core. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.struts:struts2-core` | Maven | From 2.3.19 | 2.3.20.3 | | `org.apache.struts:struts2-core` | Maven | From 2.3.19 | 2.3.20.3 | | `org.apache.struts:struts2-core` | Maven | From 2.3.21 | 2.3.24.3 | | `org.apache.struts:struts2-core` | Maven | From 2.3.21 | 2.3.24.3 | | `org.apache.struts:struts2-core` | Maven | From 2.3.25 | 2.3.28.1 | | `org.apache.struts:struts2-core` | Maven | From 2.3.25 | 2.3.28.1 | Products: Apache Struts. ## How do I fix CVE-2016-3087? Upgrade org.apache.struts:struts2-core to a fixed version for your release line: 2.3.20.3, 2.3.24.3 or 2.3.28.1. ## Is CVE-2016-3087 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-3087 exists. Public exploit code: - Apache Struts REST Plugin With Dynamic Method Invocation Remote Code Execution (metasploit) - Apache Struts - REST Plugin With Dynamic Method Invocation Remote Code Execution (Metasploit) (exploitdb) - Apache Struts - REST Plugin With Dynamic Method Invocation Remote Code Execution (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-9791](https://insights.sbomify.com/CVE-2017-9791/): Apache Struts 1 Improper Input Validation (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) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2016-3087 and fix it if it is affected. What it is: CVE-2016-3087 is a critical code injection vulnerability in Apache Struts, published on 7 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-3087 exists. Affected packages and fixed versions: - org.apache.struts:struts2-core (Maven): affected from 2.3.19; fixed in 2.3.20.3 - org.apache.struts:struts2-core (Maven): affected from 2.3.19; fixed in 2.3.20.3 - org.apache.struts:struts2-core (Maven): affected from 2.3.21; fixed in 2.3.24.3 - org.apache.struts:struts2-core (Maven): affected from 2.3.21; fixed in 2.3.24.3 - org.apache.struts:struts2-core (Maven): affected from 2.3.25; fixed in 2.3.28.1 - org.apache.struts:struts2-core (Maven): affected from 2.3.25; fixed in 2.3.28.1 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-2016-3087/ (Markdown: https://insights.sbomify.com/CVE-2016-3087/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2016-3087 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-3087 - OSV: https://osv.dev/vulnerability/CVE-2016-3087 --- From sbomify Insights: https://insights.sbomify.com/CVE-2016-3087/ Summaries are generated and may contain mistakes; the official description above is the record.