Skip to content

Deserialization of Untrusted Data in Flamingo amf-serializer

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

Package

maven com.exadel.flamingo.flex:amf-serializer (Maven)

Affected versions

<= 2.2.0

Patched versions

None

Description

The Java implementation of AMF3 deserializers used in Flamingo amf-serializer by Exadel, version 2.2.0, may allow instantiation of arbitrary classes via their public parameter-less constructor and subsequently call arbitrary Java Beans setter methods. The ability to exploit this vulnerability depends on the availability of classes in the class path that make use of deserialization. A remote attacker with the ability to spoof or control information may be able to send serialized Java objects with pre-set properties that result in arbitrary code execution when deserialized.

References

Published by the National Vulnerability Database Jun 11, 2018
Published to the GitHub Advisory Database May 13, 2022
Last updated Dec 22, 2023
Reviewed Dec 22, 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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

2.392%
(90th percentile)

Weaknesses

CVE ID

CVE-2017-3202

GHSA ID

GHSA-j88v-q3vw-p9vr

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.