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.
References
Link | Resource |
---|---|
https://www.kb.cert.org/vuls/id/307983 | Third Party Advisory US Government Resource |
https://issues.apache.org/jira/browse/FLEX-35290 | Issue Tracking Vendor Advisory |
http://mail-archives.apache.org/mod_mbox/flex-dev/201703.mbox/%3C6B86C8D0-6E36-48F5-AC81-4AB3978F6746@c-ware.de%3E | Mailing List Patch Vendor Advisory |
http://www.securitytracker.com/id/1038273 | Broken Link |
http://www.securityfocus.com/bid/97383 | Broken Link |
https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03823en_us | Third Party Advisory |
https://www.zerodayinitiative.com/advisories/ZDI-22-507/ | Third Party Advisory VDB Entry |
https://www.zerodayinitiative.com/advisories/ZDI-22-506/ | Third Party Advisory VDB Entry |
Information
Published : 2017-12-28 07:29
Updated : 2022-04-19 09:06
NVD link : CVE-2017-5641
Mitre link : CVE-2017-5641
JSON object : View
CWE
CWE-502
Deserialization of Untrusted Data
Products Affected
hp
- xp_command_view_advanced_edition
apache
- flex_blazeds