# CVE-2017-3202: Deserialization of Untrusted Data in Flamingo amf-serializer

> Remote attackers can achieve arbitrary code execution by sending malicious serialized objects to applications using the vulnerable Flamingo AMF serializer library.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j88v-q3vw-p9vr

## What is CVE-2017-3202?

CVE-2017-3202 is a critical unsafe deserialization vulnerability in Exadel Flamingo amf-serializer, published on 11 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-913 (Improper Control of Dynamically-Managed Code Resources)

## Which versions are affected by CVE-2017-3202?

2 open source packages ship an affected version, including com.exadel.flamingo.flex:amf-serializer. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.exadel.flamingo.flex:amf-serializer` | Maven | All versions to 2.2.0 | None |
| `com.exadel.flamingo.flex:amf-serializer` | Maven | All versions to 2.2.0 | None |

Products: Exadel Flamingo.

## How do I fix CVE-2017-3202?

No fix has been published for CVE-2017-3202 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-3202 being exploited?

There is no known exploitation of CVE-2017-3202 in the wild and no public exploit code.

## Other vulnerabilities in Exadel Flamingo amf-serializer

- [CVE-2017-3206](https://insights.sbomify.com/CVE-2017-3206/): XML external entity in Flamingo amf-serializer (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3202 and fix it if it is affected.

What it is: CVE-2017-3202 is a critical unsafe deserialization vulnerability in Exadel Flamingo amf-serializer, published on 11 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3202 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.exadel.flamingo.flex:amf-serializer (Maven): affected all versions up to 2.2.0; no fix listed
- com.exadel.flamingo.flex:amf-serializer (Maven): affected all versions up to 2.2.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-3202/ (Markdown: https://insights.sbomify.com/CVE-2017-3202/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-3202
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-3202
- OSV: https://osv.dev/vulnerability/CVE-2017-3202

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-3202/
Summaries are generated and may contain mistakes; the official description above is the record.