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
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Apache Software Foundation | Apache Flex Blaze DS | before 4.7.3 | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Maven | org.apache.flex.blazeds:flex-messaging-core | < 4.7.3 | 4.7.3 | GHSA-w8v7-prhw-xjpw |
| Maven | org.apache.flex.blazeds:flex-messaging-remoting | < 4.7.3 | 4.7.3 | GHSA-w8v7-prhw-xjpw |
References
- VU#307983 third-party-advisory
- 97383 vdb-entry
- 1038273 vdb-entry
- [flex-dev] 20170327 [VOTE] Release Apache Flex BlazeDS 4.7.3 mailing-list
- https://issues.apache.org/jira/browse/FLEX-35290
- https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03823en_us
- https://www.zerodayinitiative.com/advisories/ZDI-22-507/
- https://www.zerodayinitiative.com/advisories/ZDI-22-506/