Debian has issued an advisory on November 24: https://www.debian.org/security/2015/dsa-3403 This issue is explained further in this long oss-security thread: http://openwall.com/lists/oss-security/2015/11/09/1 One useful link from that thread that explains the issue concisely is here: https://blogs.apache.org/foundation/entry/apache_commons_statement_to_widespread This issue will not be assigned a CVE, but applications that use this library in an unsafe manner could receive CVEs. Mageia 5 is also affected. Reproducible: Steps to Reproduce:
CC: (none) => geiger.david68210Whiteboard: (none) => MGA5TOO
URL: (none) => http://lwn.net/Vulnerabilities/665805/
apache-commons-collections-3.2.2-1.mga6 uploaded for Cauldron by David.
Version: Cauldron => 5Whiteboard: MGA5TOO => (none)
RedHat has issued an advisory for this on November 30: https://rhn.redhat.com/errata/RHSA-2015-2522.html Apparently, RedHat assigned the CVE themselves after MITRE declined to. LWN reference for the CVE: http://lwn.net/Vulnerabilities/666320/
Summary: apache-commons-collections new deserialization security issue fixed upstream in 3.2.2 => apache-commons-collections new deserialization security issue fixed upstream in 3.2.2 (CVE-2015-7501)
URL: http://lwn.net/Vulnerabilities/665805/ => http://lwn.net/Vulnerabilities/666320/
Patched package uploaded for Mageia 5. Advisory: ======================== Updated apache-commons-collections packages fix security vulnerability: It was found that the Apache commons-collections library permitted code execution when deserializing objects involving a specially constructed chain of classes. A remote attacker could use this flaw to execute arbitrary code with the permissions of the application using the commons-collections library (CVE-2015-7501). With this update, deserialization of certain classes in the commons-collections library is no longer allowed. Applications that require those classes to be deserialized can use the system property "org.apache.commons.collections.enableUnsafeSerialization" to re-enable their deserialization. References: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7501 https://blogs.apache.org/foundation/entry/apache_commons_statement_to_widespread https://rhn.redhat.com/errata/RHSA-2015-2522.html ======================== Updated packages in core/updates_testing: ======================== apache-commons-collections-3.2.1-24.1.mga5 apache-commons-collections-testframework-3.2.1-24.1.mga5 apache-commons-collections-javadoc-3.2.1-24.1.mga5 apache-commons-collections-testframework-javadoc-3.2.1-24.1.mga5 from apache-commons-collections-3.2.1-24.1.mga5.src.rpm
Assignee: mageia => qa-bugsSeverity: normal => critical
CC: (none) => davidwhodginsWhiteboard: (none) => advisory
Trying x64: apache-commons-collections-3.2.1-24.1.mga5 The update went smoothly. I stopped/re-started httpd. All valid local web accesses work fine. For me this update is OK, but it does not touch the issue in question. Others please test.
CC: (none) => lewyssmith
This has nothing to do with httpd. As long as the update installs cleanly, you can OK it.
Tried to figure out how to actually test it, with no luck, so going ahead and validating it, as it does install cleanly.
Keywords: (none) => validated_updateWhiteboard: advisory => advisory MGA5-64-OKCC: (none) => sysadmin-bugs
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGASA-2016-0012.html
Status: NEW => RESOLVEDResolution: (none) => FIXED