CVE-2017-5641
Critical
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.
SeverityCritical
CVSS9.8
Exploit probability—
Product
Apache Flex Blazeds
PublishedDec 28, 2017
First seenDec 28, 2017
How to fix
Update
- hp xp_command_view_advanced_edition8.5.3-00 or later
- org.apache.flex.blazeds:flex-messaging-core4.7.3 or later
- org.apache.flex.blazeds:flex-messaging-remoting4.7.3 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| apache flex_blazeds | v ≤ 4.7.2 | — |
| hp xp_command_view_advanced_edition | v < 8.5.3-00 | 8.5.3-00 |
| org.apache.flex.blazeds:flex-messaging-coreMaven | v < 4.7.3 | 4.7.3 |
| org.apache.flex.blazeds:flex-messaging-remotingMaven | v < 4.7.3 | 4.7.3 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
In the Intelligence 360 plan
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.