Not rated
CVE-2017-5641 Previous versions of Apache Flex BlazeDS (4.7.2 and earlier) did not restrict which types were allowed for AMF(X) object…
Description
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.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Apache Flex Blaze DS | Versions not published |
References
- VU#307983 www.kb.cert.org
- 97383 www.securityfocus.com
- 1038273 www.securitytracker.com
- [flex-dev] 20170327 [VOTE] Release Apache Flex BlazeDS 4.7.3 mail-archives.apache.org
- issues.apache.org issues.apache.org
- support.hpe.com support.hpe.com
- www.zerodayinitiative.com www.zerodayinitiative.com
- www.zerodayinitiative.com www.zerodayinitiative.com
Timeline
- Published
- Last modified