Flamingo amf-serializer by Exadel, version 2.2.0, Action Message Format (AMF3) Java implementation is vulnerable to insecure deserialization

published 2018-06-11 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-12325

cvss: 8.1; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 5.2%; EPSS 5.2% chance of exploitation in 30 days, percentile 92%
public exploits: 0; none known

The Java implementation of AMF3 deserializers used in Flamingo amf-serializer by Exadel, version 2.2.0 derives class instances from java.io.Externalizable rather than the AMF3 specification's recommendation of flash.utils.IExternalizable. A remote attacker with the ability to spoof or control an RMI server connection may be able to send serialized Java objects that execute arbitrary code when deserialized.

Exploit prediction

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

Exploits and checks

codewhitesec.blogspot.com https://codewhitesec.blogspot.com/2017/04/amf.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.1	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

Exadel Flamingo amf-serializer

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

References

codewhitesec.blogspot.com /2017/04/amf.html
exploit, third-party-advisory
kb.cert.org /vuls/id/307983
third-party-advisory
securityweek.com /flaws-java-amf-libraries-allow-remote-code-execution
third-party-advisory
securityfocus.com /bid/97380
vdb-entry, third-party-advisory

Sources

CVE List CVE-2017-3201
NVD CVE-2017-3201

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.

Summary