# CVE-2018-3972: Deserialization in Epee

> A deserialization flaw in the Epee library allows remote attackers to execute arbitrary code via specially crafted network packets.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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:** 26 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4844-9f5j-f96x

## What is CVE-2018-3972?

CVE-2018-3972 is a critical unsafe deserialization vulnerability in https://github.com/sabelnikov Epee, published on 26 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An exploitable code execution vulnerability exists in the Levin deserialization functionality of the Epee library, as used in Monero 'Lithium Luna' (v0.12.2.0-master-ffab6700) and other cryptocurrencies. A specially crafted network packet can cause a logic flaw, resulting in code execution. An attacker can send a packet to trigger this vulnerability.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2018-3972?

It affects 1 product.


Products: Getmonero Monero.

## How do I fix CVE-2018-3972?

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

## Is CVE-2018-3972 being exploited?

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

## Other vulnerabilities in https://github.com/sabelnikov Epee

- [CVE-2025-26819](https://insights.sbomify.com/CVE-2025-26819/): Denial of service in Monero (high 8.6)
- [CVE-2020-26947](https://insights.sbomify.com/CVE-2020-26947/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3972 and fix it if it is affected.

What it is: CVE-2018-3972 is a critical unsafe deserialization vulnerability in https://github.com/sabelnikov Epee, published on 26 Sep 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-2018-3972 in the wild and no public exploit code.

Affected product: https://github.com/sabelnikov Epee. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2018-3972/ (Markdown: https://insights.sbomify.com/CVE-2018-3972/index.md)
```

## Sources

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

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