# CVE-2012-0392: Apache Struts's CookieInterceptor component does not use the parameter-name whitelist

> Remote attackers can execute arbitrary commands via crafted HTTP cookies in Apache Struts due to missing parameter whitelisting in the CookieInterceptor.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jan 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2ppp-xj34-vvf7

## What is CVE-2012-0392?

CVE-2012-0392 is a medium-severity code injection vulnerability in Apache Struts, published on 8 Jan 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CookieInterceptor component in Apache Struts before 2.3.1.1 does not use the parameter-name whitelist, which allows remote attackers to execute arbitrary commands via a crafted HTTP Cookie header that triggers Java code execution through a static method.

## Which versions are affected by CVE-2012-0392?

4 open source packages ship an affected version, including org.apache.struts.xwork:xwork-core and org.apache.struts:struts2-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.struts.xwork:xwork-core` | Maven | All versions | 2.2.3.1 |
| `org.apache.struts.xwork:xwork-core` | Maven | All versions | 2.2.3.1 |
| `org.apache.struts:struts2-core` | Maven | All versions | 2.2.3.1 |
| `org.apache.struts:struts2-core` | Maven | All versions | 2.2.3.1 |

Products: Apache Struts.

## How do I fix CVE-2012-0392?

Upgrade org.apache.struts.xwork:xwork-core to 2.2.3.1 or later.

## Is CVE-2012-0392 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-0392 exists.

Public exploit code:

- Apache Struts 2 < 2.3.1 - Multiple Vulnerabilities (exploitdb)
- Apache Struts2 S2-008 RCE (nuclei): http/cves/2012/CVE-2012-0392.yaml

## 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-2012-0392 and fix it if it is affected.

What it is: CVE-2012-0392 is a medium-severity code injection vulnerability in Apache Struts, published on 8 Jan 2012. 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-2012-0392 exists.

Affected packages and fixed versions:
- org.apache.struts.xwork:xwork-core (Maven): affected all versions; fixed in 2.2.3.1
- org.apache.struts.xwork:xwork-core (Maven): affected all versions; fixed in 2.2.3.1
- org.apache.struts:struts2-core (Maven): affected all versions; fixed in 2.2.3.1
- org.apache.struts:struts2-core (Maven): affected all versions; fixed in 2.2.3.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-2012-0392/ (Markdown: https://insights.sbomify.com/CVE-2012-0392/index.md)
```

## Sources

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

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