Skip to content

CVE-2017-5641 Apache Flex BlazeDS unsafe deserialization

CriticalCVSS 9.8 EPSS 20.7%
Published
Updated
Exploit status
No public exploit known

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

ProductAffected versionsFixed in
org.apache.flex.blazeds/flex-messaging-core(Maven) <= 4.7.2 No fix listed
org.apache.flex.blazeds/flex-messaging-remoting(Maven) <= 4.7.2 No fix listed
org.apache.flex.blazeds/flex-messaging-core(Maven) < 4.7.3 4.7.3
org.apache.flex.blazeds/flex-messaging-core(Maven) = 4.7.0 No fix listed
org.apache.flex.blazeds/flex-messaging-core(Maven) = 4.7.1 No fix listed
org.apache.flex.blazeds/flex-messaging-core(Maven) = 4.7.2 No fix listed
org.apache.flex.blazeds/flex-messaging-remoting(Maven) < 4.7.3 4.7.3
org.apache.flex.blazeds/flex-messaging-remoting(Maven) = 4.7.0 No fix listed
org.apache.flex.blazeds/flex-messaging-remoting(Maven) = 4.7.1 No fix listed
org.apache.flex.blazeds/flex-messaging-remoting(Maven) = 4.7.2 No fix listed
apache flex blazeds <= 4.7.2 No fix listed
HP Inc xp command view advanced edition < 8.5.3-00 8.5.3-00
Apache Flex Blaze DS = before 4.7.3 No fix listed

References