Apache Flex BlazeDS unsafe deserialization

2022-05-1301:02:10

Google

osv.dev

0.098 Low

EPSS

Percentile

94.9%

JSON

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.

CPENameOperatorVersion
org.apache.flex.blazeds:flex-messaging-coreeq4.7.0
org.apache.flex.blazeds:flex-messaging-remotingeq4.7.0
org.apache.flex.blazeds:flex-messaging-coreeq4.7.1
org.apache.flex.blazeds:flex-messaging-remotingeq4.7.1
org.apache.flex.blazeds:flex-messaging-coreeq4.7.2
org.apache.flex.blazeds:flex-messaging-remotingeq4.7.2

Name	Operator	Version
org.apache.flex.blazeds:flex-messaging-core	eq	4.7.0
org.apache.flex.blazeds:flex-messaging-remoting	eq	4.7.0
org.apache.flex.blazeds:flex-messaging-core	eq	4.7.1
org.apache.flex.blazeds:flex-messaging-remoting	eq	4.7.1
org.apache.flex.blazeds:flex-messaging-core	eq	4.7.2
org.apache.flex.blazeds:flex-messaging-remoting	eq	4.7.2