Skip to content
Fencer Intel
critical 9.8

CVE-2017-5641 in the critical feed json

Apache Flex BlazeDS unsafe deserialization

published 2017-12-28 8 y ago modified 2026-06-17 4 mo ago also GHSA-w8v7-prhw-xjpw , EUVD-2022-5535

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
20.7%
EPSS 20.7% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.flex.blazeds:flex-messaging-core 4.7.3
  • maven org.apache.flex.blazeds:flex-messaging-remoting 4.7.3
  • hp xp_command_view_advanced_edition 8.5.3-00

Exploit prediction

20.75% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.flex.blazeds:flex-messaging-core
<4.7.3
4.7.3
maven org.apache.flex.blazeds:flex-messaging-remoting
<4.7.3
4.7.3

Affected products

  • Apache Software Foundation Apache Flex Blaze DS

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.