The java.io.ObjectInputStream is known to cause Java serialisation issues. This issue here is exposed by the webtools/control/httpService URL, and uses Java deserialization to perform code execution. In the HttpEngine, the value of the request parameter serviceContext is passed to the deserialize method of XmlSerializer. Apache Ofbiz is affected via two different dependencies: commons-beanutils and an out-dated version of commons-fileupload Mitigation: Upgrade to 16.11.06 or manually apply the commits from OFBIZ-10770 and OFBIZ-10837 on branch 16
The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
|Name||Vendor||Start Version||End Version|
It is often convenient to serialize objects for communication or to save them for later use. However, deserialized data or code can often be modified without using the provided accessor functions if it does not use cryptography to protect itself. Furthermore, any cryptography would still be client-side security – which is a dangerous security assumption. Data that is untrusted can not be trusted to be well-formed. When developers place no restrictions on “gadget chains,” or series of instances and method invocations that can self-execute during the deserialization process (i.e., before the object is returned to the caller), it is sometimes possible for attackers to leverage them to perform unauthorized actions, like generating a shell.