on 25-Dec-2017 06:19
In October 2017 Oracle have published a vulnerability concerning Oracle WebLogic and assigned CVE-2017-10271 to it. Since then no public information regarding this vulnerability was available until a few days ago, when an analysis of the vulnerability and a Proof-of-Concept exploit were published.
The vulnerability stems from an unsafe XML deserialization using Java XMLDecoder in the CoordinatorPortType web service, which is part of the WLS Security component of WebLogic.
Attackers may send a crafted XML document to the aforementioned web service which will cause WebLogic to deserialize it and consequently allow an attacker to construct arbitrary Java objects and invoke their methods resulting in remote code execution.
Figure 1: Part of the request exploiting the vulnerability.
BIG-IP ASM customers under any supported BIG-IP version are already protected against this 0-day vulnerability, as the exploitation attempt will be detected by an existing Java code injection attack signature (200004174) which can be found in signature sets that include “Server Side Code Injection” attack type or “Java Servlets/JSP” System.
Figure 2: Exploitation attempt blocked by signature id 200004174.
We will be also releasing a dedicated signature in the upcoming ASM Security Update.
We download the last signature list and added this signature but the signature that blocks our test request is 200004336 "Oracle WebLogic WLS Security component Remote Code Execution" with Last Updated date 12/26/2017. I assume this is the adopted signature to mitigate this attack.
It seems it only works for the default context root /wls-wsat/CoordinatorPortType , if we use and other context root with the same payload the signature is not triggert.
Can we have the rule body of this signature so we can make a custom one that is more generic?