CVE-2017-3201

Name: CVE-2017-3201
Creator: NVD / NIST
Published: 2018-06-11T17:29:00.57+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 5.38%

Last modified Jun 17, 2026

CVE-2017-3201 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 5.38% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability

5.38%

91.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions
Exadel	Flamingo Amf-Serializer	2.2.0

References

http://www.securityfocus.com/bid/97380Third Party Advisory, VDB Entry
http://www.securityweek.com/flaws-java-amf-libraries-allow-remote-code-executionThird Party Advisory
https://codewhitesec.blogspot.com/2017/04/amf.htmlExploit, Third Party Advisory
https://www.kb.cert.org/vuls/id/307983Third Party Advisory
http://www.securityfocus.com/bid/97380Third Party Advisory, VDB Entry
http://www.securityweek.com/flaws-java-amf-libraries-allow-remote-code-executionThird Party Advisory
https://codewhitesec.blogspot.com/2017/04/amf.htmlExploit, Third Party Advisory
https://www.kb.cert.org/vuls/id/307983Third Party Advisory

Timeline

Published: Jun 11, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-3201?

How severe is CVE-2017-3201?

Severity scoring for CVE-2017-3201 is pending analysis. The EPSS model estimates a 5.38% probability of exploitation in the next 30 days.

How do I fix CVE-2017-3201?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-3201?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST