CVE-2012-4386
Last modified
CVE-2012-4386 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.45% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Struts | 2.0.0 |
| Apache | Struts | 2.0.1 |
| Apache | Struts | 2.0.2 |
| Apache | Struts | 2.0.3 |
| Apache | Struts | 2.0.4 |
| Apache | Struts | 2.0.5 |
| Apache | Struts | 2.0.6 |
| Apache | Struts | 2.0.7 |
| Apache | Struts | 2.0.8 |
| Apache | Struts | 2.0.9 |
| Apache | Struts | 2.0.10 |
| Apache | Struts | 2.0.11 |
| Apache | Struts | 2.0.11.1 |
| Apache | Struts | 2.0.11.2 |
| Apache | Struts | 2.0.12 |
| Apache | Struts | 2.0.13 |
| Apache | Struts | 2.0.14 |
| Apache | Struts | 2.1.0 |
| Apache | Struts | 2.1.1 |
| Apache | Struts | 2.1.2 |
| Apache | Struts | 2.1.3 |
| Apache | Struts | 2.1.4 |
| Apache | Struts | 2.1.5 |
| Apache | Struts | 2.1.6 |
| Apache | Struts | 2.1.8 |
| Apache | Struts | 2.1.8.1 |
| Apache | Struts | 2.2.1 |
| Apache | Struts | 2.2.1.1 |
| Apache | Struts | 2.2.3 |
| Apache | Struts | 2.2.3.1 |
| Apache | Struts | 2.3.1 |
| Apache | Struts | 2.3.1.1 |
| Apache | Struts | 2.3.1.2 |
| Apache | Struts | 2.3.3 |
| Apache | Struts | 2.3.4 |
References
- http://secunia.com/advisories/50420Vendor Advisory
- http://struts.apache.org/2.x/docs/s2-010.htmlVendor Advisory
- http://secunia.com/advisories/50420Vendor Advisory
- http://struts.apache.org/2.x/docs/s2-010.htmlVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2012-4386?
How severe is CVE-2012-4386?
How do I fix CVE-2012-4386?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2012
- CVE-2012-4380MediaWiki before 1.18.5, and 1.19.x before 1.19.2 allows rem…
- CVE-2012-4381MediaWiki before 1.18.5, and 1.19.x before 1.19.2 saves pass…8.1
- CVE-2012-4382MediaWiki before 1.18.5, and 1.19.x before 1.19.2 does not p…
- CVE-2012-4383contao prior to 2.11.4 has a sql injection vulnerability8.8
- CVE-2012-4384letodms has multiple XSS issues: Reflected XSS in Login Page…6.1
- CVE-2012-4385letodms 3.3.6 has CSRF via change password6.5
- CVE-2012-4387Apache Struts 2.0.0 through 2.3.4 allows remote attackers to…
- CVE-2012-4388The sapi_header_op function in main/SAPI.c in PHP 5.4.0RC2 t…
- CVE-2012-4389Incomplete blacklist vulnerability in lib/migrate.php in own…
- CVE-2012-4390(1) apps/calendar/appinfo/remote.php and (2) apps/contacts/a…
- CVE-2012-4391Cross-site request forgery (CSRF) vulnerability in core/ajax…
- CVE-2012-4392index.php in ownCloud 4.0.7 does not properly validate the o…
Are you affected by CVE-2012-4386?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
