Common Vulnerabilities and Exposures assigned an identifier CVE-2012-0392 to the following vulnerability: Name: CVE-2012-0392 URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0392 Assigned: 20120108 Reference: BUGTRAQ:20120105 SEC Consult SA-20120104-0 :: Multiple critical vulnerabilities in Apache Struts2 Reference: http://archives.neohapsis.com/archives/bugtraq/2012-01/0031.html Reference: EXPLOIT-DB:18329 Reference: http://www.exploit-db.com/exploits/18329 Reference: https://lists.immunityinc.com/pipermail/dailydave/2012-January/000011.html Reference: https://www.sec-consult.com/files/20120104-0_Apache_Struts2_Multiple_Critical_Vulnerabilities.txt Reference: http://struts.apache.org/2.x/docs/s2-008.html Reference: http://struts.apache.org/2.x/docs/version-notes-2311.html Reference: SECUNIA:47393 Reference: http://secunia.com/advisories/47393 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.
This issue only affects struts 2.
Statement: A previous statement by Red Hat related to this CVE, prior to August 2019, said that Apache Struts 2 is not included in any Red Hat products. This earlier statement was incorrect. While Struts 2 is not actively compiled, shipped, used, or enabled in any Red Hat provided final products, and does not cause any vulnerability in the product, struts2-core jars have been included in some products' source code packages. The inclusion was part of an import of the Google Guice repository, which includes struts2-core. Customers that build artefacts from our source code could be at risk. Red Hat will remove these artefacts from source code in future releases. The products that included the Struts 2 artefacts in their source jars: Fuse Service Works 6.0.0 Single Sign On 7.3.0+ If you have used the source package from one of these products to build artefacts on your system, you should do the following to remove potentially affected jars: 1. Run 'find . -name struts2*.jar' under the source location 2. Remove any files found This will not affect the product, as the jar is included with the source of google-guice, but no functionality requiring struts2 is implemented.