# CVE-2012-4386: Cross-Site Request Forgery in Apache Struts

> Remote attackers can bypass CSRF protections in Apache Struts by manipulating token configuration, allowing unauthorized actions on behalf of users.

- **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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2rvh-q539-q33v

## What is CVE-2012-4386?

CVE-2012-4386 is a medium-severity vulnerability in Apache Struts, published on 5 Sep 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The token check mechanism in Apache Struts 2.0.0 through 2.3.4 does not properly validate the token name configuration parameter, which allows remote attackers to perform cross-site request forgery (CSRF) attacks by setting the token name configuration parameter to a session attribute.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

2 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.0.0 | 2.3.4.1 |
| `org.apache.struts:struts2-core` | Maven | From 2.0.0 | 2.3.4.1 |

Products: Apache Struts.

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

Upgrade org.apache.struts:struts2-core to 2.3.4.1 or later.

## Is CVE-2012-4386 being exploited?

There is no known exploitation of CVE-2012-4386 in the wild and no public exploit code.

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

What it is: CVE-2012-4386 is a medium-severity vulnerability in Apache Struts, published on 5 Sep 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-4386 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.struts:struts2-core (Maven): affected from 2.0.0; fixed in 2.3.4.1
- org.apache.struts:struts2-core (Maven): affected from 2.0.0; fixed in 2.3.4.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-4386/ (Markdown: https://insights.sbomify.com/CVE-2012-4386/index.md)
```

## Sources

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

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