How severe is CVE-2012-0393?

No CVSS score has been assigned to CVE-2012-0393 yet. Review the advisory details and affected package list to assess your exposure.

Which products are affected by CVE-2012-0393?

Affected package information for CVE-2012-0393 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2012-0393?

Apply the apache struts security patch or hotfix for CVE-2012-0393 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2012-0393 across my infrastructure?

Inventory every apache struts deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2012-0393 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2012-0393?

O3 detects and blocks CVE-2012-0393 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2012-0393 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2012-0393, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is CVE-2012-0393?

CVE-2012-0393 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2012-0393?

CVE-2012-0393 affects apache struts. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2012-0393 published, and has it been updated?

CVE-2012-0393 was published on January 8, 2012 and was last updated on June 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2012-0393

CVE-2012-0393 is a CWE-264 vulnerability in apache struts. 4 public exploit references exist, so weaponization risk is real. O3 Security detects and blocks CVE-2012-0393 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

The ParameterInterceptor component in Apache Struts before 2.3.1.1 does not prevent access to public constructors, which allows remote attackers to create or overwrite arbitrary files…

Published

Jan 8, 2012

Updated

Jun 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

4 known

Description

The ParameterInterceptor component in Apache Struts before 2.3.1.1 does not prevent access to public constructors, which allows remote attackers to create or overwrite arbitrary files via a crafted parameter that triggers the creation of a Java object.

Affected Products

1 product · 1 configurations

Application

strutsapache

≥ 2.1.0 && < 2.3.1.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-18329webappsmultiple✓ Verified

Apache Struts 2 < 2.3.1 - Multiple Vulnerabilities

by SEC Consult · Jan 6, 2012

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every apache struts deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the apache struts security patch or hotfix for CVE-2012-0393 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2012-0393 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2012-0393. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2012-0393 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2012-0393 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2012-0393

Description

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2012-0393 being exploited in your environment?