Page History

...

You were though still at risk if you use used RMI, JNDI, JMX or Spring and maybe other Java classes we don't use OOTB in OFBiz. So we (the PMC ) decided to comment out RMI OOTB 

We also decided to provide a simple way to protect yourself from protect OFBiz instances from all possible Java serialization vulnerabilities. While working on the serialization vulnerability, I stumbled upon this article "Closing the open door of java object serialization" and decided notsoserial was the solution we needed. It's now embedded in OFBiz and called by all running Gradle taks. It easily protects you from all possible serialization vulnerabilities as explained here!To be safe in case you use RMI for instance, use one of the start*-secure ant targets or use the JVM arguments those targets use.the notsoserial project. The idea is simple: initially you don't know what to put in your whitelist because there are some objects in OFBiz you need to put there, plus the ones you add yourself. So you use an empty whitelist and with the dryrun option you specify a file where the serialized objects are listed. Then you can continuously fill your whitelist to keep things secure. You can use the trace option to get a better idea of where and why an object is serialized.