# CVE-2020-17752: Integer overflow in n/a

> An integer overflow in the payable function of an Ethereum token smart contract allows attackers to manipulate token balances or logic.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 24 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-chj7-x4mx-v4qg

## What is CVE-2020-17752?

CVE-2020-17752 is a critical vulnerability in n/a, published on 24 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow vulnerability in payable function of a smart contract implementation for an Ethereum token, as demonstrated by the smart contract implemented at address 0xB49E984A83d7A638E7F2889fc8328952BA951AbE, an implementation for MillionCoin (MON).

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2020-17752?

It affects 1 product.


Products: Mon Project Mon.

## How do I fix CVE-2020-17752?

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

## Is CVE-2020-17752 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-17752 and fix it if it is affected.

What it is: CVE-2020-17752 is a critical vulnerability in n/a, published on 24 Jun 2021. 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-2020-17752 in the wild and no public exploit code.

Affected product: n/a. 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-2020-17752/ (Markdown: https://insights.sbomify.com/CVE-2020-17752/index.md)
```

## Sources

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

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