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 security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Flex BlazeDS | <=4.7.2 | |
Hp Xp Command View Advanced Edition | <8.5.3-00 | |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.