First published: Thu Dec 28 2017(Updated: )
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.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.apache.flex.blazeds:flex-messaging-remoting | <=4.7.2 | 4.7.3 |
maven/org.apache.flex.blazeds:flex-messaging-core | <=4.7.2 | 4.7.3 |
Cisco Nexus Dashboard Fabric Controller | ||
Apache BlazeDS | <=4.7.2 | |
HP P9000 Command View Advanced Edition Software | <8.5.3-00 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-5641 is classified as a medium severity vulnerability due to its potential to execute code during object deserialization.
To fix CVE-2017-5641, upgrade to Apache Flex BlazeDS version 4.7.3 or later.
CVE-2017-5641 affects all types that are allowed for AMF(X) object deserialization in Apache Flex BlazeDS versions prior to 4.7.3.
The consequences of CVE-2017-5641 include the potential execution of arbitrary code if an attacker crafts a specific serialized object.
Yes, CVE-2017-5641 can be particularly dangerous for applications that use AMF serialization without proper validation or restrictions.