Skip to content

Apache Flex BlazeDS unsafe deserialization

Critical severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Oct 6, 2023

Package

maven org.apache.flex.blazeds:flex-messaging-core (Maven)

Affected versions

<= 4.7.2

Patched versions

4.7.3
maven org.apache.flex.blazeds:flex-messaging-remoting (Maven)
<= 4.7.2
4.7.3

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.

References

Published by the National Vulnerability Database Dec 28, 2017
Published to the GitHub Advisory Database May 13, 2022
Reviewed Jul 25, 2023
Last updated Oct 6, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

7.439%
(94th percentile)

Weaknesses

CVE ID

CVE-2017-5641

GHSA ID

GHSA-w8v7-prhw-xjpw

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.