Previous versions of Apache Flex BlazeDS (4.7.2 and earlier) did not restrict which types were allowed for AMF(X) object deserialization by default. During the deserialization process code is executed that for several known types has undesired side-effects. Other, unknown types may also exhibit such behaviors. One vector in the Java standard library exists that allows an attacker to trigger possibly further exploitable Java deserialization of untrusted data. Other known vectors in third party libraries can be used to trigger remote code execution.
CPE | Name | Operator | Version |
---|---|---|---|
flex_blazeds | le | 4.7.2 | |
xp_command_view_advanced_edition | eq | < 8.5.3-0 |
mail-archives.apache.org/mod_mbox/flex-dev/201703.mbox/%[email protected]%3E
www.securityfocus.com/bid/97383
www.securitytracker.com/id/1038273
issues.apache.org/jira/browse/FLEX-35290
support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03823en_us
www.kb.cert.org/vuls/id/307983
www.zerodayinitiative.com/advisories/ZDI-22-506/
www.zerodayinitiative.com/advisories/ZDI-22-507/