Hi all,
Apache team has announced a new commons collections release:
http://archive.apache.org/dist/commons/collections/binaries/ to fix this
vulnerability:
http://www.infoworld.com/article/3003197/security/library-misuse-exposes-lea
ding-java-platforms-to-attack.html
Would this be the way to apply this fix? We are currently running Sakai2.9.3
I found commons-collections-3.2.jar under the gradebook tool. So I plan to change the version in the gradebook tool pom.xmlI also searched all pom.xml in our build for 'commons-collection' and came
up with 56 of them.
Would I change all the version number in all of these pom.xml files?I also found commons-collections-3.2.1.jar under <tomcat_home>/shared/lib; would someone know what I need to change so that the build script will pick up the 3.2.2 version?--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+...@apereo.org.
To post to this group, send email to saka...@apereo.org.
Visit this group at http://groups.google.com/a/apereo.org/group/sakai-dev/.
Serialization support for unsafe classes in the functor package is disabled by default as this can be exploited for remote code execution attacks. To re-enable the feature the system property "org.apache.commons.collections.enableUnsafeSerialization" needs to be set to "true". Classes considered to be unsafe are: CloneTransformer, ForClosure, InstantiateFactory, InstantiateTransformer, InvokerTransformer, PrototypeCloneFactory, PrototypeSerializationFactory, WhileClosure.